DO NOT REPLY [Bug 6663] New: - Adding trigger class in web app means that the class can not be found

[bu...@apache.org]

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=6663>.
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=6663

Adding trigger class in web app means that the class can not be found

           Summary: Adding trigger class in web app means that the class can
                    not be found
           Product: Tomcat 4
           Version: 4.0.2 Final
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: bk@avolent.com


In my environment, I added a trigger class (e.g. javax.xml.*) in my web app.
This causes the class loader to not find the class at all even if it is
installed in one of the inherited class loaders. If this is added as a jar
file,the jar is skipped but the class could still be found. However, if adding
as a class file it will never be found because findClassInternal() method throws
a ClassNotFoundExeption. 

This ClassNotFound is not intuitive. More intuitive would be what is done with
the jar files, ignore the class in question (with a warning). If the code is
operating according to spec, then more information/docs should be provided as to
the real cause of the exception.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>