commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34661] - [logging][PATCH] Improvements to LogFactoryImpl
Date Mon, 06 Jun 2005 10:52:51 GMT
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=34661>.
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=34661





------- Additional Comments From skitching@apache.org  2005-06-06 12:52 -------
(In reply to comment #30)
oops - small but critical typo. I'll try again...

Re scenario (1) of comment#29: Consider tomcat's classloader hierarchy:
  http://jakarta.apache.org/tomcat/tomcat-5.5-doc/class-loader-howto.html
 
Log/LogFactory/LogFactoryImpl is deployed at the "system" level (this is
standard out-of-the-box configuration for tomcat).
 
Now if someone deploys JCL at the "webapp" level *and* at the shared or common
level deploys Log4JLog+log4j but not Log, then you have a situation where:
  * TCCL [webapp] fails (Log duplicated)
  * parent of TCCL [shared] succeeds (and is *not* LFICL).

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message