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 ------- Additional Comments From [EMAIL PROTECTED] 2002-03-08 17:43 ------- A skeptic ... that's good, it never fails to make you feel good to report problems only to be told that well they are imaginary... but seriously... There are no changes to the classes. All we did was to upgrade to Tomcat 4.0.3. The same code base runs without problems on the other server which is still on Tomcat 2.3.3. Re WebappClassLoader as the parent of custom class loaders... This is not a feasable proposition. Consider that the servlet may be using third party libraries already packaged into JARs which in their turn may define custom class loaders. Since one has no access to the code... no way to ensure that all custom class loaders use WebappClassLoader as their parent! The servlet container should support java class loaders without adding on specific requirements!!! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
