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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2002-03-08 18:04 ------- Two points: - Creating CL and/or forking threads both violate the J2EE model, so doing either of these can create problems. So no, the container doesn't have to "support java class loaders without adding on specific requirements". - The WebappClassLoader is the context class loader for the thread which invokes your servlet. If it's not the parent of your new CL, it won't work, because the JARs of your webapp are only present in this CL repositories. So overall, I would say this "WORKSFORME" if the CL creation is done properly (please attach some sample code if you think something is broken, becasue otherwise, it's hard to speculate on what your code is doing). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
