P1
Problem statement:
1. Siebel client run on JRE 1.4.2_02 and + .
2. Siebel client is not the only software which will be installed on the client machine, as Siebel can not control or monitor these environments once deployment is over.
3. It is happening in real world Scenario, that some other S/W with lower JRE version from JRE 1.3.1 series will get installed on the same system, which happens after Siebel Client with JRE 1.4.2_02 + gets installed.
4. In that case, applet ceased to work on the browser and does not detect that JRE 1.4.2 is already installed on the system, rather than that it just starts downloading the same JRE referring to Dynamic classid tag in the applet from Sun's site. Which is One part of the problem.
5. Once this is downloaded also the behavior is strange in terms of showing only MODIFY and REMOVE options for the current JRE.
If u select MODIFY also , it fails to load an applet at the end...
This is replicated at CLIENT SITE as well as at SUN INDIA LABS.
###@###.### 2005-2-23 10:31:10 GMT
1. Siebel client run on JRE 1.4.2_02 and + .
2. Siebel client is not the only software which will be installed on the client machine, as Siebel can not control or monitor these environments once deployment is over.
3. It is happening in real world Scenario, that some other S/W with lower JRE version from JRE 1.3.1 series will get installed on the same system, which happens after Siebel Client with JRE 1.4.2_02 + gets installed.
4. In that case, applet ceased to work on the browser and does not detect that JRE 1.4.2 is already installed on the system, rather than that it just starts downloading the same JRE referring to Dynamic classid tag in the applet from Sun's site. Which is One part of the problem.
5. Once this is downloaded also the behavior is strange in terms of showing only MODIFY and REMOVE options for the current JRE.
If u select MODIFY also , it fails to load an applet at the end...
This is replicated at CLIENT SITE as well as at SUN INDIA LABS.
###@###.### 2005-2-23 10:31:10 GMT