JDK-6659026 : 6u10(Nightly) : Jar cache versioning is not working with latest nightly bundles
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-02-04
  • Updated: 2010-09-08
  • Resolved: 2008-02-21
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 b12Fixed
Related Reports
Relates :  
JDK-6632521 - Plugin2 : Jar Cache Versioning information is not working properly with new model
Relates :  
JDK-6606784 - Add support for launching applets from JNLP files
Relates :  
JDK-6659532 - PIT b12: Java Console can not be closed or invoked through system tray icon
Description
Feature is broken again from nightly build-Feb01.
Steps to reproduce
----------------
1) Install latest PIT-08 bundles
2) Set permissions to all inside .java.policy
3) Run following applet using singlejar.jar with version 0.0.0.1
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/cachingtest/new/TestSJ_Carchive.html
 Run following applet using same jar i.e. singlejar.jar with version 0.0.0.2
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/cachingtest/new/TestSJ_Carchversion.html
5)Make sure that  output on Java console should display information about jar versioning.
6) Invoke Java control panel and view the files under Jar cache viewer as follows
Java Control Panel > View > Resources
There should be 2 enteries against singlejar.jar with different versions
If not then bug is reproduced
Switch to old Plug-in using JCP and everything will work fine
This is a regression of 6632521.
Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6659026.0
05-02-2008
EVALUATION An inadvertent change to the initialization order caused the com.sun.deploy.Environment class to think that it wasn't running in the context of the Java Plug-In, and therefore disabled jar versioning support. Fixed the initialization order, added an explicit run-time check for this situation, and made the code resilient with respect to it.
05-02-2008