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=15009>. 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=15009 Classloading behavior does not follow specification/documentation ------- Additional Comments From [EMAIL PROTECTED] 2002-12-03 08:25 ------- I agree, the previous implementation of the WebappClassLoader did have its issues too. However, the "delegation" attribute offered at least a choice. Wouldn't it make sense to retain this degree of freedom? (!delegation && !filter(name)) ---> delegation order: webapp -> bootstrap -> system -> common -> shared (corresponds to the behavior described in the spec, default behavior of Tomcat 4.0.x) (delegate || filter(name)) ---> delegation order: bootstrap -> system -> common -> shared -> webapps (current default behavior of Tomcat 4.1.12) filter(name) is true if name starts with a package name from the trigger list. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
