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-19 09:23 ------- I'm not sure about your factory map talking but consider this. log4j can do what I want without problems. It is rather simple, when you want to have your own instance, you need the jar file in your own class loader. In a proper j2ee environment (child first delegation), this will always lead to a new logger instance). I agree that jboss's UnifiedClassLoader is a problem in that regard. But I see it this way. If you want to have your own logging instance, then work without that damned UnifiedClassLoader. The thing is that these 'Inter-App' Calls are happening all the time. jmx-console: The TCCL is the WebClassLoader and the current is the one of the MBean (Application) jmx-scheduling: The TCCL is the one of the TimerMBean (jboss or jdk) and the current is the one of the MBean (Application) JCAPoolFiller Thread: The TCCL is the jboss-one and the current is the Applications ClassLoader. I think that my a approach can still work. 1. Try commons-logging approach first (TCCL) 2. If no logger is found (not assignable?) try the current class loader Agreed it might not always be the correct logging instance, but at least it would not generate an error and the log would be written. -- 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]
