DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37054>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37054 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-13 05:09 ------- It is the responability of your custom Loader to correctly resolve the parent ClassLoader (by calling getParentClassLoader on the Container). It's possible that the Tomcat developers could make this easier for people extending WebappLoader (which is why I'm not actually closing the bug), but in the meantime, something like: public void start() throws LifecycleException { Thread cthrd = Thread.currentThread(); ClassLoader oldcl = cthrd.getContextClassLoader(); cthrd.setContextClassLoader(getContainer().getParentClassLoader()); super.start(); cthrd.setContextClassLoader(oldcl); } should do as a work-around. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
