[slf4j-user] Use in WebSphere

[Ceki Gulcu]

Ben Tomasini wrote:
> 
> 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?  

SLF4J was created in part as a response to a very lengthy discussion
on the commons-dev list, early 2005. Richard Sitze was a key
participant in that discussion [1]. At a later time, I believe that it
was Richard who integrated JCL into Websphere. (I am mentioning this
as an historical snippet with no ill will towards Richard or blaming
him of any wrongdoing.)

Over the years, I have witnessed that merely replacing
commons-logging.jar with the jcl-over-slf4j.jar + slf4j-api.jar
combination solves various class loading related problems. Without
looking into each specific case, it is not possible to explain why
replacing commons-logging.jar with jcl-over-slf4j.jar + slf4j-api.jar,
but it does. As I am unaware of the specifics of JCL and Webspehere
integration, I can't comment on if and why "IBM screwed up commons
logging".

SLF4J is designed around static binding which has proven to be very
robust. However, if you really wanted, you could transform SLF4J to
use dynamic binding like JCL does. SLF4J would then be
indistinguishable from JCL in its behaviour.

HTH,

[1] http://marc.info/?l=jakarta-commons-dev&m=110686632913457&w=2

> Thanks,
> 
> Ben

-- 
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch