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 Sun, 06 Feb 2005 20:13:44 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 remm@apache.org  2005-02-06 21:13 -------
Please reread my comments. I am calling ugli a fork of commons-logging, which is
accurate. It would be much more productive to enhance commons-logging instead
(as long as API compatibility is preserved). The code is very small (as is
ugli's code).

log4j predates java.logging, of course, but it's been years now, and there have
been no efforts or progress to support it. I think it's safe to say that few
people care about whatever design issues might exist with java.logging (I am
fairly certain it is good enough, overall, since the small subset which is
commons-logging is good enough for us right now), and they would have been very
grateful to avoid having to use stuff like commons-logging. I am also fairly
certain usage of log4j would be even higher, and, on a personal standpoint, I
would be a happy camper :)

Obviously, contributions to java.logging original design are nice, but in the
end it does not matter if log4j does not support it (or if java.logging had
failed altogether, which, unfortunately or not, is not the case). I do not
actually care about java.logging, all I want is to not have 2 different
incompatible logging APIs at the end. Many people apparently think the same way,
as they are now standardizing on commons-logging to get unified configuration
for all components.

Since the API problem is at the root of nearly all of the issues we've had (CL
issues, etc), I think the way this could have been avoided is fairly clear, and
you could have avoided whatever all the bugs that were caused by the use of
commons-logging.

Anyway, I'd like to point out this bug report was about enhancements to
java.logging support in Tomcat, not about replacing whatever logging API we use
with log4j or (that's new) one of its "child" APIs. This is a recurrent "candid"
proposal, and is getting old.


-- 
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