logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: [v2] No JUL component?
Date Sat, 10 Nov 2012 23:01:55 GMT
Yes, I've considered it but JUL really kinda sucks.

There are two ways to bridge it that I know of:
1. The way SLF4J does as documented at http://www.slf4j.org/legacy.html#jul-to-slf4j bridge.
This essentially creates a LogHandler that accepts all events and then passes them to the
replacement framework.  This has a fairly significant performance penalty.
2. Replace the LogManager as documented at http://docs.oracle.com/javase/6/docs/api/java/util/logging/LogManager.html.
Unfortunately, this requires a System Property be set before logging is initialized.  This
is the option I would most likely pick.

It is unfortunate that this wasn't updated when ServiceLoaders were added to Java.


On Nov 10, 2012, at 1:00 PM, Gary Gregory wrote:

> HI All,
> Did we ever consider a JUL component for v2? If not, it would be nice to document why.
> Gary
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

View raw message