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=35774>. 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=35774 ------- Additional Comments From [EMAIL PROTECTED] 2005-07-18 14:37 ------- JBoss Class Loader A (commons-logging available here) Application B with ClassLoader B. Child of A Application C with ClassLoader C. Child of C (commons-logging deployed in here) We have a Child First delegation as is appropriate in a J2EE Container! Application B initiates thread and makes a call to Application C. Application C contains the commons-logging in its own classloader C. We need this in order to have our own logging instance apart from the jboss instance. The Log interface used in application C is loaded by ClassLoader C as it is a 'static' link. commons-logging will take the Log implementation from the TCCL which either comes from CL B or CL A. None of them will implement Log from CL C. This is a fairly common case in jboss. The horror is that we do not even use commons-logging directly, but a lot of third-party does. That and the fact that commons-logging is part of the jboss distribution and visiable to all applications, even if I have isolated class loaders. -- 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]
