Tested using mantis beta 10. Happens on all platform.

current splash screen structure will associate the main jar file of the
jnlp application with the splash icon. However, if two or more jnlp
application use the same main jar file, but has different splash icon,
JWS can not distiguish them.

An example:
http://sqesvr.sfbay.sun.com/deployment2/yuwang/development/bug/https_proxy2.jnlp
http://sqesvr.sfbay.sun.com/deployment2/yuwang/development/bug/https_proxy3.jnlp

the only difference is that they use different splash image.
If you launch one of them, then launch another, you will see that
the splash screen is still the old one. You have to clear cache to
download the corresponding splash icon.

The reason is that inside splash.xml file, the association is jar-image
matching, like this:
http\://sqesvr.sfbay/deployment2/yuwang/development/bug/jar/hellojaws.jar=/home/yuwang/.java/.deployment/javaws/cache/splashes/splash7104.jpg

I think the correct association should be jnlp-image matching. One jnlp
represents one application, then one application has one icon or splash
screen.

Such scenario will not be uncommon in customer environment. Customer may have
one major jar file to act as start point, then run different functionality
based on different setting in the jnlp file.

###@###.### 2002-12-15