JDK-6634145 : Adding a JRE entry to the Javaws runtime pops up "Java Plug-in Settings Changed" dialog
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2007-11-27
  • Updated: 2011-02-16
  • Resolved: 2008-02-25
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 :  
Relates :  
Description
Tested build :6u10b07 promoted build / 6u10b08 PIT
Teserd OS    :Windows XP,Vista
Steps to reproduce:
---------------------
1.Install Kernel JRE/Normal JRE
2.Open Java Control Panel and Select Java Tab.
3.Click View button in JNLP Application Runtime Settings.
4.Add a JRE entry in the  table displaying the installed JRE versions in User tab of  JNLP Runtime Systems dialog and Click OK.
5.Click Apply/OK button in Java Control Panel.
6."Browser Settings Changed"  information dialog is displayed.

The information dialog is not present till 6u10b05.As this is an unexpected dialog the test fail during automation.Also,the text of the dialog is irrelevant as the chnage is done to JNLP runtime settings.
All the tests from  suite_javaws_controlpanel are failing because of this unexpected popup dialog during automation.
This popup dialog appears only on machines where Mozilla is installed.
In jlab420.india.sun.com (vncpwd:vnc123) this was not reproducible as there was no Mozilla installed.After installing mozilla (1.7.8) the bug is reproducible on this machine also.
Its reproducible in 6u10b10 also ,but the Information dialog's text is changed.
Now its "Java-Plug In Settings Changed.
Changes to the next-generation Java Plug-in option will be in effect after restart of browser(s) "

1.Clear cache & Install Kernel JRE/Normal JRE
2.Open Java Control Panel and Select Java Tab.
3.Click View button in JNLP Application Runtime Settings.
4.Add a JRE entry in the  table displaying the installed JRE versions in User tab of  JNLP Runtime Systems dialog and Click OK.
5.Click Apply/OK button in Java Control Panel.
6.Information dialog is displayed.with text -"Java-Plug In Settings Changed.
Changes to the next-generation Java Plug-in option will be in effect after restart of browser(s) " 
7.Now ,this dialog comes only once,after an installation.On Next attempt there is no dialog displayed.Till b09 the "Browser Settings Changed" dialog was coming every time.

Comments
EVALUATION From Java Control Panel, if one adds a JRE from the Java Application Runtime Settings, the "Java Plug-in Settings Changed" is always pops up when the Java Control Panel is run for the first time after JRE installation or when the "Enable the next-generation Java Plug-in" is selected in a subsequent invocation of the Java Control Panel. Other than the annoying dialog, the problem is more severe because it unselects the new Java Plug-in when the user tries to add a JRE from the Java Application Runtime Settings. It is due to when a JRE is being added, JavawsTableModel.refresh() calls into Config.refreshUnchangedProps() which resets the new Java Plug-in related property (deployment.jpi.mode.new). Therefore, when ControlPanel.apply() is called when the user clicks on the "Ok" button, the deployment.jpi.mode.new property is set to false at that point and the code within ControlPanel.apply() unselects the new Java Plug-in and pops up the mentioned dialog. A fix is to populate the property in JavawsTableModel after the refreshUnchangedProps() call. The JQS selection in the Java Control Panel also has the exact issue due to this bug. If JQS has been select and the user adds a JRE from the Java Application Runtime Settings, the JQS will be unselected silently. The fix fixes the JQS issue as well.
23-01-2008

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6634145.1
23-01-2008

EVALUATION This was reported agains 6u10 b07 and b08. I have tested agains b10, and cannot reproduce. please confirm that this can no longer be reproduced with B10 and I will close, or provide additional steps to help me reproduce on 6u10 b10.
17-01-2008