You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-cvs@jakarta.apache.org by ce...@apache.org on 2002/03/06 14:31:48 UTC
cvs commit: jakarta-log4j/src/xdocs download.xml index.xml
ceki 02/03/06 05:31:48
Modified: src/xdocs download.xml index.xml
Log:
Changed category refereces to logger on the introduction page.
Also changed the indentation.
Revision Changes Path
1.48 +6 -6 jakarta-log4j/src/xdocs/download.xml
Index: download.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/xdocs/download.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- download.xml 18 Feb 2002 23:40:38 -0000 1.47
+++ download.xml 6 Mar 2002 13:31:48 -0000 1.48
@@ -54,16 +54,16 @@
</section>
- <section name="log4j version 1.2 beta3">
- <p>log4j 1.2 beta 3 is now available in <a
- href="../jakarta-log4j-1.2beta3.tar.gz"><b>TAR.GZ</b></a>
+ <section name="log4j version 1.2 beta4">
+ <p>log4j 1.2 beta 4 is now available in <a
+ href="../jakarta-log4j-1.2beta4.tar.gz"><b>TAR.GZ</b></a>
format or in <a
- href="../jakarta-log4j-1.2beta3.zip"><b>ZIP</b></a> format.
+ href="../jakarta-log4j-1.2beta4.zip"><b>ZIP</b></a> format.
</p>
<p>In addition to many performance improvements, bug fixes, and
- other small enhancements, log4j 1.2 beta3 adds JMX support,
+ other small enhancements, log4j 1.2 beta4 adds JMX support,
Mapped Diagnostic Contexts, and buffered IO capability. One
important change is the replacement of the Category class with
Logger class and the Priority with the Level in order to
@@ -71,7 +71,7 @@
</p>
<p>All changes except the removal of deprecated methods are backward
- compatible such that log4j 1.2beta3 can be considered a drop in
+ compatible such that log4j 1.2beta4 can be considered a drop in
replacement for log4j 1.1.3. </p>
</section>
1.8 +56 -53 jakarta-log4j/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/xdocs/index.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- index.xml 8 Feb 2002 13:23:30 -0000 1.7
+++ index.xml 6 Mar 2002 13:31:48 -0000 1.8
@@ -10,60 +10,63 @@
<body>
+ <section name="Introduction">
+ <p>Inserting log statements into your code is a low-tech method
+ for debugging it. It may also be the only way because
+ debuggers are not always available or applicable. This is
+ often the case for distributed applications.</p>
+
+ <p>On the other hand, some people argue that log statements
+ pollute source code and decrease legibility. (We believe that
+ the contrary is true). In the Java language where a
+ preprocessor is not available, log statements increase the
+ size of the code and reduce its speed, even when logging is
+ turned off. Given that a reasonably sized application may
+ contain thousands of log statements, speed is of particular
+ importance.</p>
+
+
+ <p>With log4j it is possible to enable logging at runtime
+ without modifying the application binary. The log4j package is
+ designed so that these statements can remain in shipped code
+ without incurring a heavy performance cost. Logging behavior
+ can be controlled by editing a configuration file, without
+ touching the application binary.</p>
+
+ <p>Logging equips the developer with <i>detailed context</i> for
+ application failures. On the other hand, testing provides
+ quality assurance and confidence in the application. Logging
+ and testing should not be confused. They are
+ complementary. When logging is wisely used, it can prove to be
+ an essential tool.</p>
+
+ <p>One of the distinctive features of log4j is the notion of
+ <i>inheritance</i> in loggers. Using a logger
+ <em>hierarchy</em> it is possible to control which log
+ statements are output at arbitrarily fine granularity but also
+ great ease. This helps reduce the volume of logged output and
+ minimize the cost of logging.</p>
+
+ <p>The target of the log output can be a file, an
+ <code>OutputStream</code>, a <code>java.io.Writer</code>, a
+ remote log4j server, a remote Unix Syslog daemon, or even a NT
+ Event logger among many other output targets.</p>
+
+ <p>On a 233 MHz ThinkPad running JDK 1.1.7B, it costs about 46
+ nanoseconds to determine if that statement should be logged or
+ not. Actual logging is also quite fast, ranging from 79
+ microseconds using the SimpleLayout, 164 microseconds using
+ the TTCCLayout and around a millisecond when printing
+ exceptions. The performance of the PatternLayout is almost as
+ good as the dedicated layouts, except that it is a lot more
+ flexible.</p>
+
+ <p>The package is being constantly improved thanks to input from
+ users and code contributed by authors in the community.
+ </p>
-
-<section name="Introduction">
-
-<p>Inserting log statements into your code is a low-tech method for
-debugging it. It may also be the only way because debuggers are not
-always available or applicable. This is often the case for
-distributed applications.</p>
-
-<p>On the other hand, some people argue that log statements pollute
-source code and decrease legibility. (We believe that the contrary is
-true). In the Java language where a preprocessor is not available,
-log statements increase the size of the code and reduce its speed,
-even when logging is turned off. Given that a reasonably sized
-application may contain thousands of log statements, speed is of
-particular importance.</p>
-
-
-<p>With log4j it is possible to enable logging at runtime without
-modifying the application binary. The log4j package is designed so
-that these statements can remain in shipped code without incurring a
-heavy performance cost. Logging behavior can be controlled by editing
-a configuration file, without touching the application binary.</p>
-
-<p>Logging equips the developer with <i>detailed context</i> for
-application failures. On the other hand, testing provides quality
-assurance and confidence in the application. Logging and testing
-should not be confused. They are complementary. When logging is wisely
-used, it can prove to be an essential tool.</p>
-
-<p>One of the distinctive features of log4j is the notion of
-<i>inheritance</i> in categories. Using a category <em>hierarchy</em>
-it is possible to control which log statements are output at
-arbitrarily fine granularity but also great ease. This helps reduce
-the volume of logged output and minimize the cost of logging.</p>
-
-<p>The target of the log output can be a file, an
-<code>OutputStream</code>, a <code>java.io.Writer</code>, a remote
-log4j server, a remote Unix Syslog daemon or even a NT Event logger.</p>
-
-<p>On a 233 MHz ThinkPad running JDK 1.1.7B, it costs about 46
-nanoseconds to determine if that statement should be logged or
-not. Actual logging is also quite fast, ranging from 79 microseconds
-using the SimpleLayout, 164 microseconds using the TTCCLayout and
-around a millisecond when printing exceptions. The performance of the
-PatternLayout is almost as good as the dedicated layouts, except that
-it is a lot more flexible.</p>
-
-<p>The package is being constantly improved thanks to input from users
-and code contributed by authors in the community.</p>
-
-</section>
-
-</body>
+ </section>
+ </body>
</document>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>