Am 06.07.2011 20:34, schrieb Chris Dolan:
2) attaching OSGi bundle context to each log message. When you have the same class in multiple bundles and want to know where the message really came from, this is important
Interesting - and how do you use the bundle context in your log messages or in your appender configuration? Is there a special pattern like e.g. %bsn for the bundle symbolic name?
On a related note, I have implemented a private logback backend for pax-logging-api (replaces pax-logging-service) and hope to release it someday soon when I get a few upstream Logback bugs fixed (it currently must include logback in Bundle-Classpath and replaces ch.qos.logback.classic.spi.LoggingEvent, which fails on an unchecked cast)
Sounds good - I hope you'll get round to publish a preview soon :-) Cheers, Harald _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
