|
Quick Lists
|
|
Bug ID:
|
4773110
|
|
Votes
|
0
|
|
Synopsis
|
Apps are run with the wrong JRE
|
|
Category
|
javawebstart:other
|
|
Reported Against
|
1.2
, jaws-1.0-fcs
|
|
Release Fixed
|
1.4.2(mantis)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
4723634
,
4828440
|
|
Submit Date
|
04-NOV-2002
|
|
Description
|
When the applications JRE specification (such as version="1.3+) matches
more than one configured JRE, the spec says the latest JRE will be used.
Currently the native launching code uses the first one that matches.
|
|
Work Around
|
For apps running before this fix, if both 1.2.2 and 1.3 are present when 1.4 is
asked for, 1.2.2 may be run, which can't download 1.4.
to work around this:
Have 2 jnlp files. the first one (MyApp1.jnlp) has the following:
<jnlp spec="1.0" codebase="..." href="MyApp2.jnlp">
<j2se version="1.4.1+ 1.3+"/>
In the second jnlp file (MyApp2.jnlp) have the following:
<jnlp spec="1.0" codebase="..." href="MyApp2.jnlp">
<j2se version="1.4.1+"/>
Have the link on the net point to the first jnlp file. The browser
will download it, and the native code will launch java 1.3.X , since
that matches the specified version="1.4.1+ 1.3+". The java code will
then download the right jnlp file and request 1.4.1 from java.sun.com.
but now it should work since it will be running 1.3.x.
xxxxx@xxxxx 2002-11-21
|
|
Evaluation
|
fix this in matchVersionString in configurationFile.h for mantis
xxxxx@xxxxx 2002-11-04
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
