JDK-6697478 : Still some issues with passing runtime args via JCP
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2008-05-05
  • Updated: 2010-09-08
  • Resolved: 2008-06-13
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 b26Fixed
Related Reports
Relates :  
JDK-6749040 - Runtime settings are not applied in classic Plug-In with "-rc2" version string
Description
Build Tested : 6u10 b-23
Issues related to passing of runtime args via JCP got FIXED as part of bug 6685605 in b-23 but it has been noticed that bug has not FIXED properly. Mainly we have 2 following important issus which needs to be addressed ASAP:
1) Passing runtime args via JCP is not working at all for old Plug-in. This is a regression
2) For new Plug-in , not all paramaters are getting passed correctly e.g. -verbose

Steps to reproduce:
------------------
Issue #1
1) Invoke JCP > Advanced > Java Plug-in
  - Uncheck option "Enable the next generation Plug-in" and "Apply" changes
  - GO to JCP > Java > Java Applet runtime Settings > View
  - Set runtime settings as -Xint
2) Run following applet inside the browser
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/runtimeArgs/TestApplet.html
 - If the VM info is getting displayed as "mixed mode" then issue #1 is reproduced
Close the browser
3) Invoke JCP > Advanced > Java Plug-in
  - Check option "Enable the next generation Plug-in" 
4) Run the same applet again inside the browser
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/runtimeArgs/TestApplet.html
 - This time one can notice that everything is working correctly  as VM info is getting displayed as "interpreted mode"

Issue #2
1) Invoke JCP > Java > Java Applet runtime Settings > View
  - Set runtime settings as -verbose
  - Save changes
2) Invoke same applet again unside th ebrowser
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/runtimeArgs/TestApplet.html
    If a windows console does not open up conatniing outputs all the method calls, classes etc. then issue #2 is reproduced
Comments
EVALUATION Old plugin code must use the 'javaws' ones as well, as the new plugin does (lately). However, no security behavioral change shall be made to the old plugin. It is expected that the old plugin will reach EOL (end of life) soon.
14-05-2008