JDK-6705941 : JNLP JREDesc selections fails in case of multiple JREDesc entries
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-05-22
  • Updated: 2010-09-08
  • Resolved: 2008-06-16
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
Duplicate :  
Description
In case of multiple JREDesc entries in the root JNLP file (other are ignored),
we have to select either the first one for which a JRE is installed,
or - if non is installed, the first JREDesc entry.

This is currently not working.

Example:
    <java version="1.2" java-vm-args="-esa">
        <resources>
            <property name="sun.java2d.d3d" value="ERROR"/>
        </resources>
    </java>
    <java version="1.7 1.6" java-vm-args="-da">
        <resources>
            <property name="sun.java2d.d3d" value="true"/> <!-- property # 2 -->
        </resources>
    </java>
    <java version="1.5.9 1.5*" java-vm-args="-ea"/>

Comments
SUGGESTED FIX Actually implementing the JREDesc selecting, the way as it is specified (see description).
22-05-2008

EVALUATION see fix ..
22-05-2008