logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject RE: Log4J vs Java 1.4 Logging
Date Thu, 22 May 2003 07:46:29 GMT
At 11:40 PM 5/21/2003 -0400, you wrote:


>Lo4j's API was enhanced to match the JDK API a while back.  see
>http://www.qos.ch/logging/thinkAgain.html.

I am uncomfortable with the statement "log4j API was enhanced to match
the JDK API a while back." When JSR47 was under public review, we
lobbied to make improvements to the JDK 1.4 logging API. If you look
at https://www.qos.ch/ac2001/F11-200.html, on the right column you
will see that the JDK 1.4 logging API had many serious shortcomings prior
to spec. version 0.75.

1) Order of configuration of loggers had an influence. So if you
configured a child logger before parent, the parent would override the
child's configuration. Sigh.

2) Appenders (or handlers) were not cumulative. Loggers would only log
to the appenders directly attached to them. Another sigh.

3) I'll stop at two.

The only change log4j underwent was to rename Category class as Logger
and the Priority class as Level. The actual method signatures or
implementations did not change at all except those mandated by the
name change. In summary, we did not log4j was not enhanced when JSR47
came out, only two classes were renamed. Interestingly enough, it was
quite a challenge to retain backward compatibility, but that is a
different story...



>Mike

--
Ceki  For log4j documentation consider "The complete log4j manual"
       ISBN: 2970036908  http://www.qos.ch/shop/products/clm_t.jsp 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org


Mime
View raw message