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=36852>. 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=36852 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2006-04-20 08:54 ------- Ive been developing using Eclipse and the Sysdeo plugin (http://www.sysdeo.com/eclipse/tomcatplugin) and I found that it worked fine right up until we started using tomcat 5.5.12. Consequently I picked up the source and started digging. I found that when the custom class loader runs using 5.5.9 the hierarchy of class loaders is : o webappX (WebappClassloader) o Shared (StandardClassloader) o Common (StandardClassloader) o System (AppClassloader) o Bootstrap (ExtClassloader) But when 5.5.12 (and up) are used it becomes: o webappX (WebappClassloader) o System (AppClassloader) o Bootstrap (ExtClassloader) Consequently the class loader stops working. I find that when my class loader works as follows public myDevLoader(ClassLoader parent) { super(parent); } which is equivalent to public myDevLoader(ClassLoader parent) { super(ClassLoader.getSystemClassLoader()); } The devloader will not find the common and shared class loaders however if I do the following . public myDevLoader(ClassLoader parent) { super(Thread.currentThread().getContextClassLoader()); } Then the devloader works as it should. -- 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]
