Hi, Am Dienstag, den 08.03.2011, 08:25 +0000 schrieb Bertrand Delacretaz: > Hi, > > On Tue, Mar 8, 2011 at 8:51 AM, Felix Meschberger <[email protected]> wrote: > > ...I think we should forget about the OSGi LogListener in this context.... > > I agree that if we have a better way to intercept logging messages, we > don't necessarily need to have the OSGi LogListener. > > 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. Regards Felix
