Hello, JCL's conflicts with the default library and configuration in the WebSphere root classpath make it a problem child for WebSphere shops. (See http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions, search WebSphere).
As I have suggested the use of SJF4J to a WebSphere shop, a common question I get is, "If IBM screwed up commons logging for us, what will stop them from doing the same with SLF4J?". Is there anything inherent in the design of SJF4J that makes this less likely? Thanks, Ben _______________________________________________ user mailing list [email protected] http://www.slf4j.org/mailman/listinfo/user
