On Sunday 11 February 2007 12:45, Tim Moloney wrote: > Hopefully, these bundles are useful enough for others to start using > them. If they need refinement, perhaps others smarter than me on the > above topics can improve them as needed.
The improvement already exist; http://wiki.ops4j.org/confluence/display/ops4j/Pax+Logging ;o) api : The internal api used for inter-bundle communication, as well as some common APIs such as JDK util Logging and KFLog. log4j : Log4J API avalon : Avalon API slf4j : SLF4J API jcl : Commons-Logging API. service : The current service implementation uses Log4J and allows you to supply the log configuration via OSGi's Configuration Admin Service. To use; Load the legacy APIs that are needed, and use each APIs factory method as usual. The service can be reloaded with stopping the clients, to allow for feature enhancements. I am also contemplating to make Log4J backend itself more modular, so that Appenders, Filters and Formatters can be loaded separately if needed. But that work has not gotten far yet. Likewise, although it implements the OSGi Log Service API, it is not fully compliant yet in respect to LogEvents and LogReaders, but that is the target before a 1.0 release. Cheers Niclas
