[XGC-72] [PATCH] Improve exception handling when loading classpath resources fails

• Type: Bug
• Status: Open
• Resolution: Unresolved
• Affects Version/s: 1.4
• Component/s: utilities
• Environment: Operating System: All; Platform: PC
• Assignee: XML Graphics Project Mailing List
• Reporter: Dominik Stadler
• Created: 09/Aug/12 06:21
• Updated: 24/Jun/15 11:50

Description

I had one invalid .jar file where signing information was not correct. When calling ClasspathResource.loadManifests(), via ClasspathResource.getInstance(), it correctly fails with a "java.lang.SecurityException: Invalid signature file digest for Manifest main attributes", however it does not tell me which actual jar-file could not be loaded.

Please enhance exception handling in that method so that it reports which jar-file failed, e.g.

— ClasspathResource.java 2010-07-02 14:04:28.000000000 +0200
+++ ClasspathResource.java.new 2012-08-09 08:20:21.428843500 +0200
@@ -138,6 +138,8 @@
addToMapping(contentType, name, classLoader);
}
}
+ } catch (SecurityException se)

{ + throw new SecurityException("While handling " + u, se); }

catch (IOException io)

{ // TODO: Log. }