tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33143] - [PATCH] Java 1.4 loggers per context
Date Tue, 08 Feb 2005 20:48:46 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=33143>.
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=33143





------- Additional Comments From william.barker@wilshire.com  2005-02-08 21:48 -------
(In reply to comment #22)
> "When packaged right" JCL will only use java.util.logging, isn't that
> a fact? Remy, have your *ever* used Tomcat with log4j in a production
> environment?
I use Tomcat with log4j in production all the time.  It works very well, when 
packaged right ;-).

> I guess that the people using commons-logging probably do not realize
> how badly JCL is broken. Given that you yourself admit not having
> being familiar with the JCL implementation, you apparently do not
> understand that JCL is much more complicated than UGLI.

Of course JCL is much more complicated than UGLI, since UGLI expects you to 
create a properties file on the CP, and is useless if you forget (you don't 
even get log4j :).  However, IMHO, that complication is necessary for logging 
in a container environment.  

I'm also -1 on having UGLI Tomcat code, and +0 for having an optional example 
of j.u.l.LogManager.


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


Mime
View raw message