JDK-6632521 : Plugin2 : Jar Cache Versioning information is not working properly with new model
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2007-11-20
  • Updated: 2010-09-08
  • Resolved: 2008-01-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6u10 b09Fixed
Related Reports
Duplicate :  
JDK-6633383 - Game applets fail to load
Relates :  
JDK-6659026 - 6u10(Nightly) : Jar cache versioning is not working with latest nightly bundles
Relates :  
JDK-6639334 - jar version information still not being honored
Description
With new Plug-in the jar cache versioning is not working properly. Archives with cache versioning information should get dumped to the deployment cache dir but that's not happening with new Plug-in.
Steps to reproduce
----------------
1) Install latest PIT-08 bundles
2) Invoke following testcases inside the IE browser
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/cachingtest/new/TestMJ_CA_CV.html
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/cachingtest/new/TestMJ_CA_CVNew.html

Close the browser
3) Invoke Java Control Panel > General > View
One can notice 2 enteries against archive a.jar with versions 1.0.0.123 and 0.0.0.123

4) Remove both the a.jar enteries from the cache viewer and close the cache viewer
5) From Java control panel switch to new Plug-in as follows
JCP > Advanced tab > Java Plug-in 
Check the oprion  "Enable the next...."
Close the JCP
6) Invoke the above mentioned applets again inside the IE browser

7) Invoke Java Control Panel > General > View
If you notice only one a.jar entry and that's also without any verion then bug is reproduced
Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6632521.0
07-12-2007
EVALUATION It was discovered that the system property "javaplugin.version" is significant to some of the common deployment code, in particular the com.sun.deploy.Environment class, which is queried by the com.sun.deploy.cache.DeployCacheHandler when determining whether to consider jar version IDs coming from the applet tag. Set this and the javaplugin.nodotversion properties to values obtained from the new autogenerated SecurityBaseline.java, which is semantically equivalent to how the old plug-in set these properties in CJavaJNI.cpp. This fix also fixes the problems with the Club Pogo premium game applets.
07-12-2007
EVALUATION The new plug-in wasn't defining the "javaplugin.version" system property during startup, which is queried by the Environment class to indicate whether it is running in the context of the Java Plug-In and which affects how the DeployCacheHandler handles jar versions. This was previously done in native code in CJavaJNI.cpp.
07-12-2007