JDK-6662404 : JNLP applet support does not re-launch for system property or command line argument specification
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-02-13
  • Updated: 2010-09-08
  • Resolved: 2008-03-05
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 b13Fixed
Related Reports
Relates :  
Relates :  
Description
Currently the support for launching applets from JNLP files does not properly re-launch the applet when either system properties or JVM command-line arguments are specified in the JNLP file. This support needs to be added.

Comments
SUGGESTED FIX JRERelaunch functional part 2: - relaunch criteria: jnlp jvm properties - relaunch criteria: jnlp jvm vm_args - relaunch state per applet The relaunch state is not global per JVM, but per applet. - relaunch: continue to launch at relaunch If the applet is at relaunch, it shall continue to launch, even if a relaunch criteria would hit. - fast jnlp startup at relaunch At relaunch, we shall not update and download the ressources again. - proper EmbeddedFrame dispose() at relaunch The EmbeddedFrame wasn't disposed properly, so a JOGL applet wasn't visible at relaunch. testcase: http://j2se.east.sun.com/deployment/www/tests/1.6.0_10/6662404/ webrev: http://sa.sfbay.sun.com/projects/deployment_data/6u10/6662404.2/
14-02-2008

EVALUATION see 'suggested fix'
14-02-2008