After 11 months of gestation, SLF4J version 1.0 (final) is finally out the door. For those who have not heard of it, SLF4J (Simple Logging Facade for Java) acts as a facade for various logging APIs allowing to the end-user to plug in the desired implementation at deployment time. A gradual migration path away from Jakarta Commons Logging (JCL) is also supported.
SLF4J does not rely on any special class loader machinery. In fact, the binding between SLF4J and a given logging API implementation is performed statically at compile time. Each binding is hardwired to use one and only specific logging API implementation. Thus, SLF4J suffers from none of the class loader problems or memory leaks observed with other approaches.
SLF4J also includes support for Marker objects, a feature which hopefully will be widely used as newer logging systems become available.
2 comments:
Just went to see www.slf4j.org and I find it difficult to make sense of all the different implementations.
I think two things may help:
1) highlight the most relevant implementations (for instance the nop implementation should not be in this list).
2) describe a few standard use-cases with the corresponding jar combination. A kind of graphical representation could be useful since the number of acronyms involved makes reading pure-text descriptions difficult.
Cheers
Thanks for the suggestions Nico. The NOP implementation has been removed from the list. As for highlighting, how can that be done and still remain fair to all implementations?
As for your 2nd suggestion, I'll add grpahical illustrations as soon as I get the time.
Post a Comment