The logback site has a page dedicated to reasons for switching: http://logback.qos.ch/reasonsToSwitch.html
An argument for logback in our project is performance. Since audit logging requirements for us are very high, logging enters into that calculation. Considering that this is the original developer of log4j (he is the principal author on both projects) claiming significant performance improvements for logback over log4j, I think the statement carries some weight. With regards to configuration, logback can be configured programmatically: http://mailman.qos.ch/pipermail/logback-dev/2009-February/003785.html http://mailman.qos.ch/pipermail/logback-dev/2009-February/003785.html http://logback.qos.ch/manual/joran.html http://logback.qos.ch/manual/joran.html http://logback.qos.ch/joran.html http://logback.qos.ch/joran.html As to implementing this ourselves, I am afraid our project is under too strict time constraints for this to be possible (also considering that we are just getting to know karaf). Except if, given the programmatic configuration possibilities, this would in fact be quite straightforward? Thanks, Sam -- View this message in context: http://karaf.922171.n3.nabble.com/Running-Karaf-without-PAX-Logging-tp3177504p3421434.html Sent from the Karaf - User mailing list archive at Nabble.com.
