Author: ceki
Date: Tue Aug 16 22:15:17 2005
New Revision: 175
Modified:
nlog4j/trunk/docs/changes.html
nlog4j/trunk/src/xdocs/changes.xml
Log:
Updated to "Changes" document
Modified: nlog4j/trunk/docs/changes.html
==============================================================================
--- nlog4j/trunk/docs/changes.html (original)
+++ nlog4j/trunk/docs/changes.html Tue Aug 16 22:15:17 2005
@@ -51,12 +51,30 @@
<h1>Differences between NLOG4J and
log4j</strong></h1>
<p>NLOG4J is a production-quality
log4j-replacement with direct
SLF4J API support. NLOG4J is maintained by Ceki G�lc�, the
- founder of the log4j project. In a nutshell, unless you invoke
- logger methods using messages of arbitrary type instead of just
- <code>String</code>, NLOG4J can be considered as a drop-in
- replacement for log4j version 1.2.9.
+ founder of the log4j project. In a nutshell, NLOG4J can be
+ considered as a drop-in replacement for log4j version 1.2.9.
</p>
- <h2><code>String</code>
instead of <code>Object</code></h2>
+ <h2>LF5, chainsaw and
<code>NTEventAppender</code></h2>
+ <p>In order to save space, it
was decided <em>not</em> to
+ bundle LF5, chainsaw and <code>NTEventAppender</code> with
+ NLOG4J.
+ </p>
+
<h1>Changes in NLOG4J 1.2.16</strong></h1>
+ <p>In NLOG4J 1.2.16, contrary to versions
1.2.14 and 1.2.15, the
+ <code>Category</code> class accepts parameters of type
+ <code>Object</code> as well as <code>String</code>.
+ </p>
+ <p>This change was introduced
to overcome compatibility problems
+ between log4j and NLOG4J. In particular, previous to NLOG4J
+ 1.2.16, software compiled with log4j would not run with NLOG4J.
+ </p>
+
<h1>Changes in NLOG4J 1.2.15</strong></h1>
+ <p>NLOG4J 1.2.15 added nominal suppport
for the
+ <code>Marker</code> interface which was added to SLF4J in
+ 1.0beta5.
+ </p>
+
<h1>Changes in NLOG4J 1.2.14</strong></h1>
+ <h2><code>String</code> instead of
<code>Object</code></h2>
<p>The
<code>org.slf4j.Logger</code> interface restricts the
type of messages that can be logged to
<code>java.lang.String</code> instead of
@@ -73,11 +91,6 @@
<code>toString()</code> invocation on the Interger object in
case the log statement is disabled for the DEBUG level. See the
<a href="http://www.slf4j.org/faq.html#2.3";>Question 2.3</a> in SLF4J
FAQ for more details.</p>
- <h2>LF5, chainsaw and
<code>NTEventAppender</code></h2>
- <p>In order to save space, it
was decided <em>not</em> to
- bundle LF5, chainsaw and <code>NTEventAppender</code> with
- NLOG4J.
- </p>
<h1>Changes in NLOG4J 1.2.14</strong></h1>
<p>Nick Faiz from the Apache Directory
project reported
compatibility issues with NLOG4J when used in conjunction with
@@ -123,10 +136,10 @@
- <hr/>
+ <hr/>
-
+
<!-- FOOTER -->
Modified: nlog4j/trunk/src/xdocs/changes.xml
==============================================================================
--- nlog4j/trunk/src/xdocs/changes.xml (original)
+++ nlog4j/trunk/src/xdocs/changes.xml Tue Aug 16 22:15:17 2005
@@ -12,24 +12,53 @@
<p>NLOG4J is a production-quality log4j-replacement with direct
SLF4J API support. NLOG4J is maintained by Ceki Gülcü, the
- founder of the log4j project. In a nutshell, unless you invoke
- logger methods using messages of arbitrary type instead of just
- <code>String</code>, NLOG4J can be considered as a drop-in
- replacement for log4j version 1.2.9.
+ founder of the log4j project. In a nutshell, NLOG4J can be
+ considered as a drop-in replacement for log4j version 1.2.9.
</p>
- <h2><code>String</code> instead of <code>Object</code></h2>
+ <h2>LF5, chainsaw and <code>NTEventAppender</code></h2>
+
+ <p>In order to save space, it was decided <em>not</em> to
+ bundle LF5, chainsaw and <code>NTEventAppender</code> with
+ NLOG4J.
+ </p>
+
+ </section>
+ <section name="Changes in NLOG4J 1.2.16">
+ <p>In NLOG4J 1.2.16, contrary to versions 1.2.14 and 1.2.15, the
+ <code>Category</code> class accepts parameters of type
+ <code>Object</code> as well as <code>String</code>.
+ </p>
+
+ <p>This change was introduced to overcome compatibility problems
+ between log4j and NLOG4J. In particular, previous to NLOG4J
+ 1.2.16, software compiled with log4j would not run with NLOG4J.
+ </p>
+
+ </section>
+
+ <section name="Changes in NLOG4J 1.2.15">
+ <p>NLOG4J 1.2.15 added nominal suppport for the
+ <code>Marker</code> interface which was added to SLF4J in
+ 1.0beta5.
+ </p>
+ </section>
+
+ <section name="Changes in NLOG4J 1.2.14">
+
+ <h2><code>String</code> instead of <code>Object</code></h2>
+
<p>The <code>org.slf4j.Logger</code> interface restricts the
type of messages that can be logged to
<code>java.lang.String</code> instead of
<code>java.lang.Object</code>.
</p>
-
+
<p>Thus, while in log4j you can write</p>
-
+
<p class="source">logger.debug(new Interger(10)); </p>
-
+
<p>in NLOG4J the previous line will not compile and needs to be
re-rewitten as:</p>
@@ -44,12 +73,6 @@
case the log statement is disabled for the DEBUG level. See the
<a href="http://www.slf4j.org/faq.html#2.3";>Question 2.3</a> in SLF4J
FAQ for more details.</p>
- <h2>LF5, chainsaw and <code>NTEventAppender</code></h2>
-
- <p>In order to save space, it was decided <em>not</em> to
- bundle LF5, chainsaw and <code>NTEventAppender</code> with
- NLOG4J.
- </p>
</section>
_______________________________________________
nlog4j-dev mailing list
[email protected]
http://slf4j.org/mailman/listinfo/nlog4j-dev
