openjdk team mailing list archive

[Mossroy <mossroy@xxxxxxxx>]

The version 6b18~pre2-1ubuntu1 of icedtea6 seems to solve this problem.
This version has been deployed through the standard upgrades of lucid

Now the page https://www.spark-angels.com/rss2/app/launch/launch_sparkangels reports a correct version number : 1.6.0_18
My test page works correctly too.
I think this bug can be closed

-- 
IcedTea6 plugin not properly detected by Sun's Deployment Toolkit Script (deployJava.js)
https://bugs.launchpad.net/bugs/525082
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.

Status in OpenJDK: Fix Released
Status in “openjdk-6” package in Ubuntu: New

Bug description:
I'm using Ubuntu 10.04 alpha 2 (with all current updates).
I installed openjdk-6 and IcedTea6 plugin (both in version 6b17-1.7-1ubuntu1)

On some web sites, the plugin (or its version) is not correctly detected.
Sun gives a "Deployment Toolkit Script" : http://java.sun.com/javase/6/docs/technotes/guides/jweb/deployment_advice.html
In fact, it's a javascript that detects the plugin and its version : http://java.com/js/deployJava.js (or http://www.java.com/js/deployJava.txt for a more human-readable version)

This script does not detect the plugin correctly. After putting a few breakpoints in it, I understood why :
- first of all, it looks for a MIME type "application/java-deployment-toolkit" or "application/npruntime-scriptable-plugin;DeploymentToolkit" and does not find it
- so it browses the MIME types, in order to find a MIME type "application/x-java-applet;jpi-version=xxx" : it finds one, and takes the xxx as the Java version. With the current IcedTea6, this reports 1.6.0_00 (instead of 1.6.0_17)

The problem is that Sun's script can be called with a minimumVersion parameter. If the minimumVersion is 1.6.0_10 for example, the check fails, and the user is redirected to the doawnload page of java.com.
This seems to be precisely what happens on this web site : http://www.sweethome3d.eu/fr/SweetHome3DOnline.jsp

I checked the behavior on Windows, with Sun's JVM 1.6.0_17 :
- the MIME type "application/npruntime-scriptable-plugin;DeploymentToolkit" is present, so Sun's script can instantiate the plugin, and get a reliable version from it
- moreover, there is a MIME-type "application/x-java-applet;jpi-version=1.6.0_17" (which is correct)

I also checked the behavior on another Ubuntu (8.10), with Sun's JVM 1.6.0_10 :
- no MIME type "application/java-deployment-toolkit" or "application/npruntime-scriptable-plugin;DeploymentToolkit" is present
- but there is a MIME-type "application/x-java-applet;jpi-version=1.6.0_10" (which is correct)


I can see two different corrections :
- the best one would be to expose one of the two MIME-types searched by the script ("application/java-deployment-toolkit" or "application/npruntime-scriptable-plugin;DeploymentToolkit"). This is a way some sites test that the java plugin is installed. The script would instantiate the plugin and get the correct version from it
- if this is not possible, the MIME type "application/x-java-applet;jpi-version=xxx" should report a correct version : 1.6.0_17 instead of 1.6.0_00