On Tue, Mar 8, 2011 at 9:31 AM, Felix Meschberger <[email protected]> wrote: > Am Dienstag, den 08.03.2011, 08:25 +0000 schrieb Bertrand Delacretaz: >> ...What's useful IMO (if it doesn't make things too complicated) is to >> have a single way of intercepting both sources of log messages, i.e. >> OSGi LogService and slf4j logging. If there's an interceptor mechanism >> for slf4j, it can probably just register as a LogListener to get both >> sources. > > This is not needed because OSGi LogService messages are ultimately > handled by the SLF4J implementation. > > So if we provide a mechanism hooking into the SLF4J implementation this > will intercept all logging message no matter what API (OSGi LogService, > SLF4J, Commons Logging, Log4J) was used to provide the message....
Ok, cool, didn't realize that - so yes, being able to intercept slf4j messages with a dynamically registered OSGi service is probably all we need. -Bertrand
