The latest Plugin Developers Guide no longer mentions the type attribute for the object tag, only for the embed tag. The Guide for 1.4 does, though. Strange.
Why is it that the applet should run on 1.5.0_09, but not on 1.5.0_06? They are API-compatible, after all. [ December 22, 2006: Message edited by: Ulf Dittmer ]
Joined: May 04, 2006
Due to some latest standards, �Sun Java Runtime Environment (JRE) - Establishes JRE version 1.5.0_09 and 1.5.0_10 as Mainstream/Standard across the Enterprise for running Java code on personal computers. Sun JRE version 1.5.0_06 and version 1.4.2_xx have been moved to the Retire/Contain phase of the TSS Technology Lifecycle.�
That's why i want to have the applet running only for the latest versions so that end users have version 1.5.0_09 or higher.
It would be great if you can tell me the solution so that the applet works only for the version 1.5.0_09 or higher.
Joined: Mar 22, 2005
If the applet failed to run on _06 due to some bug that _09/_010 fixed, I'm sure the users would tell you about it (and then they would be advised to upgrade the JVM). Until then, why worry? If corporate policy is to no longer use _06 at all, just tell the users/sys admins to uninstall it, and install the newer version. Why making the users (and your) life harder by preventing something that works?
Joined: May 04, 2006
Thats fine but we need to implement the same so that the end users follow it strictly. That's why the applet should not run with version less than 1.5.0_09.
do we any solution for the same? I am not getting as to how the versions less than 1.5.0_09 are working.
Just ran into this myself. Figured out that java 1.5 is storing the version number as 5.x.x.x
so for jre 1.5.0_11-b03 instead of using :
I checked in the registry to see what dll was being pointed to by the clsid, then browsed to the dll in windows, right click.. properties.. looked on the version tab File Version shows: 220.127.116.11 Full Version shows: 1.5.0_11-b03
I never did find a link online with this answer. Seems like it would be in a few more places.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Dynamic Versioning using JRE version 1.5.0_09