JDK-4667701 : JWS should give the name of the resource that fails
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.0.1
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2002-04-12
  • Updated: 2002-11-19
  • Resolved: 2002-11-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 mantisFixed
Description

Name: nt126004			Date: 04/12/2002


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) 
======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis
31-08-2004

EVALUATION fix for mantis fixed by fix to 4625826: unexpected exit when lazy-loading unsigned jar file ###@###.### 2002-09-17
17-09-2002