Java's native routines for reading Zip files can return detailed error
messages, but often don't. The exception therefore usually just says:
"error in opening zip file"
The mechanism for reporting in more detail is already there, and a more
specific error message would help diagnose problems: even if the main
point they communicate is "the zip file was found, there is no permissions
problem, but some problem internal to the zip file".
###@###.### 11/2/04 15:16 GMT
messages, but often don't. The exception therefore usually just says:
"error in opening zip file"
The mechanism for reporting in more detail is already there, and a more
specific error message would help diagnose problems: even if the main
point they communicate is "the zip file was found, there is no permissions
problem, but some problem internal to the zip file".
###@###.### 11/2/04 15:16 GMT
- duplicates
-
JDK-6738211 ZipFile.open error message fails to include path to (potentially corrupt) ZIP file
- Closed
- relates to
-
JDK-6190121 Jar is not usable for testing integrity of Jar files.
- Closed
-
JDK-6189491 Silent failure of corrupt Jar/Zip files during classloading yields poor diagnosability.
- Closed