: a fan; but it's really not that important any way). Then, if someone (like : me :-) would like to configure logging with log4j then I am easily empowered : to do so by removing that jar and adding slf4j-log4j.jar. What I like about
This is the part of all the third party logging abstraction arguments i've ever heard that I never understand -- if userA ruws webapp wyz.war in "CoolioServletContainer then even if wyx.war uses SLF4J, and even if userA uses slf4j-log4j.jar because userA want log4j to be the underlying logging system, that won't change the fact that unless CoolioServletContainer provides an alternate implementation of the JUL LogManager, the default implementation is still being loaded by the JVM, and some code somewhere (maybe a plugin to wyz.war, maybe another webapp in the same servlet container, etc...) might use the JUL APIs to log some info -- so userA needs to worry about those messages (or they go to STDERR). using an alternate logging framework does't make JUL logging go away -- it's still there, it's the 3000lb gorilla in the corner. it may be sleeping, but that doesn't mean some code somewhere isn't going to wake it up at some point -- you might as well acknowledge it and deal with it. bringing in another gorilla doesn't make the first one go away -Hoss
