JDK-6625756 : New Java Plug-In needs to add current JRE to available JREs in more situations
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-11-05
  • Updated: 2010-09-08
  • Resolved: 2008-01-31
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 b08Fixed
Related Reports
Relates :  
Relates :  
Description
Because the installer does not properly refresh deployment.properties, and also somewhat because the list of available JREs for the Java Plug-In in the Java Control Panel is not maintainable (see 6606278, 6606282), it is necessary for a workaround to be placed in the new Java Plug-In so it will find the current JRE it is running on top of in more situations.

The code in JVMManager.processPluginJavaInfo() needs to be changed to add the current JRE it is running on top of in more situations. Currently it only adds it if deployment.properties does not exist, or contains no listed JREs. It needs to be changed to add it in all situations *unless*:
  - there is a version of the JRE in deployment.properties matching the version it is running on top of, *and*
  - that JRE actually exists.

This workaround will have the side-effect that it will not be possible to use the Java Control Panel to remove the current JRE as an available JRE for the new Java Plug-In. However the alternative, which is that the end user must run the Java Control Panel once after installation in order to get the new plug-in to notice the availability of the current JRE (assuming deployment.properties already exists and has at least one JRE listed for the plug-in), is not acceptable.

Comments
EVALUATION Changed new plug-in to add the current JRE from which the new plug-in comes as an available JRE in almost all situations. Tested manually by modifying deployment.properties in various ways and verifying that expected JRE version was used; no regression test at this time.
06-11-2007

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6625756.1
06-11-2007