[slf4j-dev] [Bug 38] JUL bridge/router

bugzilla-daemon at pixie.qos.ch bugzilla-daemon at pixie.qos.ch
Sat Mar 1 01:49:48 CET 2008


http://bugzilla.slf4j.org/show_bug.cgi?id=38





------- Comment #2 from joern at huxhorn.de  2008-03-01 01:49 -------
Created an attachment (id=26)
 --> (http://bugzilla.slf4j.org/attachment.cgi?id=26&action=view)
Another JUL-Handler implementation...

I just implemented a java.util.logging.Handler because I one quite badly and
couldn't find one.

Then I wanted to submit it here and found this bug with the attached Handler...
*sigh*

Anyway... It has the following features:
- java.util.logging.Level is mapped to the slf4j level using
intValue-thresholds. I think it should be implemented like this because
java.util.logging gives you the ability to define your own levels by extending
Level (which I don't like at all). The intValue is used to define a relative
importance...
- I add the name of the java.util.logging.Level to the MDC. The SourceClassName
and SourceMethodName are also added if available.

I did not implement install or uninstall but documented how configuration would
look like.
A call to 
LogManager.getLogManager().reset();
should probably be added to the initialization - as I just saw while reading
Christians code :)

Feel free to take over the code if you like it. You can change the license
however it suits you.


-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the slf4j-dev mailing list