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/08 06:47:05 UTC

DO NOT REPLY [Bug 6973] New: - Custom Class loader no longer works in 4.0.3, but works in 3.2.2

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

Custom Class loader no longer works in 4.0.3, but works in 3.2.2

           Summary: Custom Class loader no longer works in 4.0.3, but works
                    in 3.2.2
           Product: Tomcat 4
           Version: 4.0.3 Final
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mpetres@netcom.ca


One of the servlets uses a custom class loader that occasionally receives class 
load requests which it forwards to the parent object using the super.loadClass
(name,resolve) method.

This loader fails to load classes using super.loadClass(name,resolve) on 4.0.3 
when the class to be loaded resides in a Jar that is under the /lib directory 
for the servlet. The code works fine in Tomcat 3.2.2!

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