http://bugzilla.qos.ch/show_bug.cgi?id=84 ------- Comment #1 from lars@koedderitzsch.net 2007-09-18 08:04 ------- Excellent analysis, I am hitting the exact same problems as the original reporter. Logback isn't ready for serious enterprise development because of the mentioned problems. My case a bit different from the ones depicted originally: b) sl4j*.jar, logback*.jar are sitting in the .ear file, the EAR contains multiple webapps (.war). Each of this webapps should log into its own context. However, because of libraries (Spring, Jakarta Commons and many more) also being shared in the ear this is impossible, because once Logger instances in the shared libs are created the initializing logger context has won. On a sidenote: Log4j has exactly the same problem, there it is the LoggerRepository which is fixed once the Logger instances are created. As I understand the Logback project wants to rise above the (for compatibility reasons) rather static Log4j. I think this would be an excellent topic for actually improving Logback over other log solutions. That being said I am quite astonished that there hasn't been a reaction from the devs on this well reasoned bug report. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.