A DESCRIPTION OF THE REQUEST :
Include the filename of the zipfile which caused the no such file or directory
exception.

Occures in all JDK version on all platforms.

JUSTIFICATION :
Starting large java applications which can use a lot of jars (ours uses 43
currently).  When something goes wrong and one is missing, we use truss to find
out which one, as the information is available in the ZipFile class adding it to
ZipExecption message would make things easier.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
java -jar test.jar
Exception in thread "main" java.util.zip.ZipException: No such file or directory test.jar
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:105)
        at java.util.jar.JarFile.<init>(JarFile.java:110)
        at java.util.jar.JarFile.<init>(JarFile.java:52)

ACTUAL -
java -jar test.jar
Exception in thread "main" java.util.zip.ZipException: No such file or directory
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:105)
        at java.util.jar.JarFile.<init>(JarFile.java:110)
        at java.util.jar.JarFile.<init>(JarFile.java:52)


---------- BEGIN SOURCE ----------
Do not need source code execute:
java -jar test.jar
in a directory that doesn't have a test.jar in it.
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
use truss
(Incident Review ID: 192698) 
======================================================================
Posted Date : 2005-12-06 17:59:03.0

N/A

Agreed.  Should be easy to fix.
  xxxxx@xxxxx   2003-08-18
As part of the work in 5010244, the launcher was changed so that when a given jar file was not found, a better message was produced.  The Zip APIs were not changed.  However, as JDC poster notes, this bug is better specified as a duplicate of 5032358.
Posted Date : 2005-12-11 16:58:52.0

Please fix this bug in J2SE 1.5

Note that this bug is a special case of bug 6290451

What on earth does this bug have to do with the launcher recognizing itself? (bug 5010244)

The root cause here is that the native code which implements ZipFile.open always throws a ZipException, not a FileNotFoundException when it should.  That has NOTHING to do with bug 5010244!  Did someone mistype the bug this bug is a duplicate of?

Did someone mean to say that this is a duplicate of bug 5032358 ?

This was a easy fix. All I need to do is to include the jar file in the command. 
so when I added this 
java -jar Test.jar 
This fixed the issue.