Name: gm110360 Date: 03/06/2003
A DESCRIPTION OF THE REQUEST :
We deploy our JNLP client from within the customers intranet from a web server.
using the object tag: a small sample follows
<OBJECT CODEBASE='plugin/j2re-1_4_1_02-windows-i586-i.exe#Version=1,4,1,2' CLASSID='clsid:5852F5ED-8BF4-11D4-A245-0080C6F74284' HEIGHT=0 WIDTH=0>
<PARAM NAME=type VALUE=application/x-java-applet>
.. ect
.. ect
</OBJECT>
EG: Our Problem, M-^Tsers have java 1.4.1_01 international on there machines
Now when we update the customers web server with a new JRE1.4.1_02 version the following should happen.
1 ) Our client starts and informs the user of an update.
2 ) client opens browser to update page, and client closes.
3 ) installation installs JRE1.4.1_02 and Jaws.
4 ) client is restarted automatically by installer if IE
or manually from desktop, by user clicking url.
Our problem is that it still starts our client with the previous JRE1.4.1_02
This kind of defeats the object of a web centric one click installation and depolyment.
JUSTIFICATION :
Our end users are no less the wiser, but if each customer has a machine park of 200 workstations, this requires a lot of support. To tell them how to manually set up web start to the correct JRE. We use the international version of JRE and by deploying this way we kan secure that the end user dose not try to use web starts auto update to 1.4 us.
EXPECTED VERSUS ACTUAL BEHAVIOR :
::End user experience:
We expect the client to start with the JRE which was just installed this would be transparent to the end user.
::Developer:
We expected Java Web Start installation to set JRE to the 1.4 version being installed.
::Note:
You do not get this problem if you have no previous installation of Java Web Start.
The previous JRE is used. We have to manually go into web start and change this for each user.
---------- BEGIN SOURCE ----------
None, use JRE 1.4.1_02 with html object tag
---------- END SOURCE ----------
(Review ID: 182202)
======================================================================