FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)

FULL OPERATING SYSTEM VERSION :

Microsoft Windows 2000 [Versjon
5.00.2195]

A DESCRIPTION OF THE PROBLEM :
We've split our application to avoid having to deploy all of it if one part
changes.
So, our JNLP-file specifies 22 jar-files under the resources-
tag.
If we fail to sign one of them, launching correctly results in an
error message.
But the message does not say which file.

In
addition, if the unsigned jar in fact should not be part of the application
and then is deleted, JWS continues to give the same error message if the
reference is not removed from the JNLP-file. The message should have been
more like "file not found" or something.

EXPECTED VERSUS ACTUAL BEHAVIOR :
I expect to be told which jar-file that is unsigned.
And that by replacing
it launching succeeds.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
An error occurred while launching/running the application.

Title:  Timesys
Local
Vendor: Norsk Hydro ASA
  Category: Security Error

Unsigned application
requesting unrestricted access to system

JNLPException[category: Security Error :
Exception: null : LaunchDesc: null ] 	at
com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source) 	at
com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source) 	at
com.sun.javaws.Launcher.continueLaunch(Unknown Source) 	at
com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source) 	at
com.sun.javaws.Launcher.handleLaunchFile(Unknown Source) 	at
com.sun.javaws.Launcher.run(Unknown Source) 	at java.lang.Thread.run(Thread.java:536)



This bug can be reproduced always.
(Review ID: 145103) 
======================================================================

N/A

fix for mantis

fixed by fix to 4625826: unexpected exit when lazy-loading unsigned jar file

 xxxxx@xxxxx  2002-09-17

Where is this fix? I still see this error in using WS 1.2 and JDK 
1.4.2? This omission has resulted in several hours of lost time. 
No doubt most people run away from Java in the client side.

I had an application with two jars specified in the jnlp file.  
The jnlp file request all permissions, but only one jar is signed.

JavaWebStart complained about the jar that is unsigned, 
showing the name of the jar file.

This is with JavaWebStart 1.4.2 only.   Only this version or 
anything above contains the bug fix.  

Do you run into similar problem with 1.4.2 webstart?