Author: ravn
Date: Sat Apr 18 21:30:01 2009
New Revision: 1319
Modified:
slf4j/trunk/slf4j-site/src/site/pages/manual.html
Log:
revised the legacy mentioning
Modified: slf4j/trunk/slf4j-site/src/site/pages/manual.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/manual.html (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/manual.html Sat Apr 18 21:30:01 2009
@@ -186,7 +186,9 @@
logging frameworks to conform to the SLF4J model.
</p>
- <h3>Libraries</h3>
+ <h3><a name="libraries"
+ href="#libraries">Libraries</a><a name="gradual"
+ href="#gradual"></a></h3>
<p>Authors of widely-distributed components and libraries may
code against the SLF4J interface in order to avoid imposing an
@@ -198,6 +200,15 @@
approach has proven to be simple and very robust.
</p>
+ <p>Those unfortunate to have to use one or more unchangable
+ legacy components which use log4j, Jakarta Commons Logging or JDK 1.4
+ logging directly, may have to use the slf4j drop-in replacements
+ which map these direct calls to slf4j. See the
+ <a href="legacy.html">Briding legacy APIs</a> page for
+ details.</p>
+
+
+
<h3><a name="mdc" href="#mdc">Mapped Diagnostic Context (MDC)
support</a></h3>
<p>"Mapped Diagnostic Context" is essentially a map maintained by the
@@ -224,13 +235,6 @@
in the logback manual.
</p>
- <h3><a name="gradual" href="#gradual">Gradual migration to SLF4J
- from Jakarta Commons Logging (JCL)</a></h3>
-
-
- <p>This section has been moved <a
- href="legacy.html#jcl-over-slf4j">elsewhere</a>.</p>
-
<h3><a name="summary" href="#summary">Executive
summary</a>
</h3>
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
