You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/03/05 20:22:30 UTC
DO NOT REPLY [Bug 6884] New: -
Need Better Error Handling in WebappClassLoader.validateJarFile
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6884>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6884
Need Better Error Handling in WebappClassLoader.validateJarFile
Summary: Need Better Error Handling in
WebappClassLoader.validateJarFile
Product: Tomcat 4
Version: 4.0.3 Final
Platform: All
OS/Version: All
Status: NEW
Severity: Minor
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: gary.mullenschultz@kingland.com
Our application stopped working when we migrated from 4.0.1 to 4.0.2; we would
get NoClassDefFoundErrors thrown for one of our classes.
This class resides in a jar file inside WEB-INF/lib. As it turns out, we had
packaged some J2SE classes (com.sun.jndi and javax.security) in that jar.
I understand the meaning of section 9.7.2 of the servlet 2.3 spec; however, I
think the current implementation needs to do one (or more) of the following so
that folks understand what's going on when they get this error:
1. Log an error of some kind. Even setting the loader to debug="99" did not
result in an error message; validateJarFile just returns false and the jar does
not get loaded.
2. Throw an exception indicating that the jar cannot be loaded, and indicate
the guilty class in question.
3. Load "acceptable" classes from the jar file, but not the offending ones.
This is a very difficult problem to debug for someone unfamiliar with the
Tomcat source code.
Thanks for a great product, Gary
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>