Skip to main content

Plugin Switching and Compatiblity

7 replies [Last post]
tom
Offline
Joined: 2003-06-11

From practical experience with a running intranet solution I have some suggestions: For applets Plugin Switching between different version of plugins can be done - but there seems to be a problem switching back to plugin 1.2.2 when plugin 1.4 is installed. This is needed for instance if 1.4 is for showing internet sites and 1.2 is needed for an intranet applet. Another useful thing would be the possiblity to combine different JRE versions in RMI applets. This would allow to update the server JRE without forcing the users to download new plugins.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
dmouse
Offline
Joined: 2003-06-09

Not sure if anyone is reading this still as this thread is a bit old, but here it goes.

What is the deployment group's thoughts regarding a switchable plugin? In the respects of having the plugin from J2SE5 for example be able to load either 1.4 or 1.5 depending on the settings specified by the user via the control panel.

I know someone posted previously the comment:
[i]Java Plug-in 1.2.2_07, 1.3.1 and higher releases supports unique CLSID and MIME types. Applet can be forced to use a particular version of Java Plug-in by using these unique MIME type/CLSID in the EMBED/OBJECT tag of the HTML page.[/i]

But I thought that once loaded a version of the plugin it was stuck with that version until you shut down the browser. Is this not true anymore?

dnp
Offline
Joined: 2006-05-05

Backward compatibility is high on our list. However, allowing JPI version switch on-the-fly within the same browser session is likely not the approach that we will take.
Latest available Java is what we'd recommend vendor to develop their apps on. We are also working with app vendors to help convert to latest Java. If you have issue converting your applet(s) to latest Java, please let us know.

jdeva
Offline
Joined: 2003-06-23

We are working on Java Plug-in and Java WebStart consolidation in 1.5 release. Both the products will have common look and feel. Java Control panel will be the common configuration tool.

tom
Offline
Joined: 2003-06-11

Thanks for your answers. We have decided to have this intranet applet extended with Webstart technology.

jdeva
Offline
Joined: 2003-06-23

Java Plug-in 1.2.2_07, 1.3.1 and higher releases supports unique CLSID and MIME types. Applet can be forced to use a particular version of Java Plug-in by using these unique MIME type/CLSID in the EMBED/OBJECT tag of the HTML page.

osbald
Offline
Joined: 2003-06-13

This might be a bit of a tangent but I'm confused as to why the Java Plugin and Java Web Start are handled separately.. each having it own independent configuration dialogs and applications - I'd like to see Web Start prefs in the control panel. Surely the proxy settings at the very least should be shared.

Now to get to my point, wouldn't Web Start's ability to handle/switch and detect different versions of the runtime actually improve Java Plugin in this respect? while Web Start would benefit from plugins more advanced proxy settings?

- Richard

tom
Offline
Joined: 2003-06-11

Sounds useful. I have no experience with webstart but for fastest applet startup our intranet solution should be extendet with it.