The fact that SLF4J does not have the class loader problems that JCL
suffers from is very much worth mentioning. In previous versions, it
was insisted upon somewhat inelegantly. However, omitting JCL's
problems as if they did not exist goes to the other extreme. This
change is attempts to strike a balance.
Thorbjoern Ravn Andersen wrote:
c...@slf4j.org skrev:
Author: ceki
Date: Fri May 29 17:28:46 2009
New Revision: 1337
Modified:
slf4j/trunk/slf4j-site/src/site/pages/manual.html
Log:
- minor rewording
- hour. Hopefully, the simplicity of the SLF4J interfaces and the
+ hour. No knowledge of class loaders is necessary as SLF4J does
+ not make use nor does it directly access any class loaders. As a
+ consequence, SLF4J suffers from none of the class loader
+ problems or memory leaks observed with Jakarta Commons Logging
+ (JCL).
+ </p>
+
+ <p>Hopefully, the simplicity of the SLF4J interfaces and the
deployment model will make it easy for developers of other
logging frameworks to conform to the SLF4J model.
</p>
Was this intentional or a slip from an old edit?
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
