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:59:50 UTC

DO NOT REPLY [Bug 6973] - 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

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Blocker                     |Major



------- Additional Comments From remm@apache.org  2002-03-08 05:59 -------
I doubt this is the case, as Jasper works like that (it creates a classloader 
to load the compiled servlets, and its parent is the webapp classloader). There 
must be some obvious problem which causes this to fail here. Is the right 
classloader set as the parent (it should be an instance of the 
WebappClassLoader class).

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