JDK-6874336 : jnlp.packEnabled and jnlp.versionEnabled should not cause any JVM relaunch
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10,6u15
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-08-20
  • Updated: 2013-11-01
  • Resolved: 2009-12-02
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.
6u18 b03Fixed 7Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Use of jnlp.packEnabled and jnlp.versionEnabled should not cause any JVM relaunch.

Right now, if specified in JNLP file only, it will relaunch JVM, for both browser applet and webstart application case.

This property is only used by webstart/plugin to determine whether we should reqest .jar.pack.gz instead of .jar for JAR download.

So as long as we set it right after we parse the JNLP file, we are good.  There is no reason to relaunch JVM because of this.

EVALUATION In ResourcesDesc, instead of reading system property to determine whether pack200 or version is enabled, it now has private boolean variables _pack200Enabled and _versionEnabled. These 2 variables will be set through the setPack200Enabled() and the setVersionEnabled() methods in ResourcesDesc from XMLFormat when it encounters the pack200Enabled or the versionEnabled property and if the property is set to true. Similar boolean variables and methods are also added to the JARDesc. In XMLFormat, after setting up an instance of ResourcesDesc, it traverses through the list of JARDesc and sets the _pack200Enabled and _versionEnabled if necessary. The changes in JVMParameters is to simplify the isExcluded() method - the check should apply to both the plugin and web start cases.