You bet, http://bugzilla.slf4j.org/show_bug.cgi?id=38 Along similar lines, I wonder if it makes sense to move log4j-bridge up to slf4j, or the jcl-bridge down into logback? Keeping all of the facade code in one place. On 2/7/07, Ceki Gülcü <listid@qos.ch> wrote:
At 05:08 PM 2/7/2007, Eric Crahen wrote:
Hi,
I've been experimenting with logback + slf4j and have been quite impressed. The slf4j API is what I write new code against, and I'm able to leverage the jcl104-over-slf4j facade and logback-log4j-bridge to intercept calls to commons logging and log4j respectively. This works really well so far. I do have one other legacy logging API that is used in some circumstances. That's the jdk14 jul api. Has anyone written a jul Handler that will route jul calls to logback? Any comments on how well that has/would work out?
Many thanks. It's always a pleasure to hear good things about one's work.
Except for bug#23 (see [1]) which is usually not blocking, the jcl104-over-slf4j bridge is known to work well for some time now. The logback-log4j-bridge is much more recent and works surprisingly well thus far. We currently use it in all our legacy systems in production.
Although we have not attempted to do so, bridging the jul API should be possible. After all, x4juli does it. Would you mind creating a bug report so that we implement this feature for the next release of logback?
[1] http://bugzilla.slf4j.org/show_bug.cgi?id=23
Thanks,
--
- Eric
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
-- - Eric