-
Bug
-
Resolution: Fixed
-
P3
-
6u10
-
b115
-
x86
-
windows_xp
-
Verified
FULL PRODUCT VERSION :
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
In Java 5, the progress dialog shown while downloading the Web Start application jars used to display our application icon as defined in the JNLP file.
In Java 6, the progress dialog shows the default Java icon instead.
This change in behavior is undocumented and unexplained.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Launch any JNLP file using Java 6 plugin.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I expected to see my application icon in the progress dialog, as was the case in Java 5.
ACTUAL -
I see the Java icon in the progress dialog instead.
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 6u10
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
In Java 5, the progress dialog shown while downloading the Web Start application jars used to display our application icon as defined in the JNLP file.
In Java 6, the progress dialog shows the default Java icon instead.
This change in behavior is undocumented and unexplained.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Launch any JNLP file using Java 6 plugin.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I expected to see my application icon in the progress dialog, as was the case in Java 5.
ACTUAL -
I see the Java icon in the progress dialog instead.
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 6u10
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.