On 5/9/06, Rob Walker <[EMAIL PROTECTED]> wrote:
The problem we had here was that the OSGi service is so minimal as to be almost useless in a real application context - except perhaps just as a bootstrapping layer for really basic startup/framework related logging. Haven't looked at SLF4J - we're still just a basic LOG4J user on what is probably quite an old version by now. Even with very very basic wiring, that turned out way better than the standard LogService though - all we really created was create: - a way for bundles to register their own log hierarchies, which they could even then configure or have a default set of application-wide config settings applied - provide a Listener registration approach to allow local bundles to register to receive LOG4J events (using pretty standard approach as I recall, although it's a long time ago) - provide an XMLRPC method for clients to register and pull back "categories" of message they are interested in (categories being used in the standard LOG4J sense)
FYI... Niclas and his crew over at www.ops4j.org have been doing some development of a comprehensive OSGi logging implementation with their pax-logging project.
