ceki 01/09/08 08:46:14
Modified: src/docbook intro.xml manual.xml
src/java/org/apache/log4j Hierarchy.java
src/sgml intro.sgml
Log:
- More doc.
_ Corrected a bug in Hiearchy#emitNoAppenderWarning method.
Revision Changes Path
1.3 +19 -10 jakarta-log4j/src/docbook/intro.xml
Index: intro.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/docbook/intro.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- intro.xml 2001/09/07 17:36:20 1.2
+++ intro.xml 2001/09/08 15:46:14 1.3
@@ -43,8 +43,9 @@
<para>As Brian W. Kernigan and Rob Pike put it in their truly
excellent book <emphasis>"The Practice of Programming"</emphasis>
+ </para>
- <blockquote>
+ <blockquote>
As personal choice, we tend not to use debuggers beyond getting a
stack trace or the value of a variable or two. One reason is that it
is easy to get lost in details of complicated data structures and
@@ -56,8 +57,8 @@
the critical section of code, even assuming we know where that
is. More important, debugging statements stay with the program;
debugging sessions are transient.
- </blockquote>
- </para>
+ </blockquote>
+
<para>Logging does have its drawbacks. It can slow down an application. If
too verbose, it can cause scrolling blindness. To alleviate these
@@ -66,14 +67,14 @@
simple to understand and to use.
</para>
-<!-- Section ----------------------------------------------------- -->
+ <!-- Section ----------------------------------------------------- -->
<sect1>
<title>Copyright</title>
<para></para>
</sect1>
-<!-- Section ----------------------------------------------------- -->
+ <!-- Section ----------------------------------------------------- -->
<sect1>
<title>Installing</title>
@@ -97,7 +98,7 @@
<!-- Section ----------------------------------------------------- -->
<sect1>
- <title>First run</title>
+ <title>First baby step</title>
<para>After you have installed <filename>log4j-VERSION.jar</filename>
in your <varname>CLASSPATH</varname>, we can try to write a small
@@ -122,15 +123,23 @@
</programlisting>
</example>
+ <caution>
+ Running this example will not produce any logging output but the
+ following warning.
+ <computeroutput>
+
+ <computeroutput>
+ </caution>
+
<para>
Using log4j in your own code is quite easy. First, you need to
import <classname>org.apache.log4j.Logger</classname> class and
then invoke the <methodname>Logger.getLogger</methodname> method
to instantiate a Logger object. Subsequently, you can invoke one
of the <link linkend="gloss-printingMethods">printing
- methods</link> of the logger, e.g. debug, to log your messages.
+ methods</link> of the logger, e.g. debug, to log your messages.
</para>
-
-</sect1>
-
+
+ </sect1>
+
</chapter>
1.3 +150 -150 jakarta-log4j/src/docbook/manual.xml
Index: manual.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/docbook/manual.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- manual.xml 2001/09/07 17:36:20 1.2
+++ manual.xml 2001/09/08 15:46:14 1.3
@@ -5,156 +5,156 @@
]>
<book lang="en">
-<bookinfo>
-<title>log4j manual</title>
-
-<author>
-<firstname>Ceki</firstname>
-<surname>Gülcü</surname>
-</author>
-
-<author>
-<firstname>Other authors</firstname>
-<surname>as appropriate</surname>
-</author>
-
-
-<revhistory>
-<revision>
-<revnumber>v1.0</revnumber>
-<date>2001-08-15</date>
-<authorinitials>cgu</authorinitials>
-</revision>
-</revhistory>
-
-<abstract>
-<para>
-This document describes the log4j API, its features and design
-rationale. Log4j is an open source project based on the work of many
-authors. It allows the developer to control which log statements are
-output with arbitrary granularity. It is fully configurable at runtime
-using external configuration files. Best of all, log4j has a gentle
-learning curve. Beware: judging from user feedback, it is also quite
-addictive.
-</para>
-</abstract>
-</bookinfo>
-
-&intro
-
-<chapter>
-<title>Architecture</title>
-<para></para>
-
-<sect1>
-<title>Selecting</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>Directing Output</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>Formatting output</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>Object Renderers</title>
-<para></para>
-</sect1>
-
-
-<sect1>
-<title>Performance</title>
-<para></para>
-</sect1>
-
-</chapter>
-
-
-<chapter>
-<title>Configuration</title>
-
-<sect1>
-<title>PropertyConfigurator</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>DOMConfigurator</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>Default configuration</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>Filters</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>Error handlers</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>Category Factories</title>
-<para></para>
-</sect1>
-
-</chapter>
-
-<chapter>
-<title>Logging in servers and other Multithreaded environments</title>
-
-<sect1>
-<title>NDC</title>
-<para></para>
-</sect1>
-
-<sect1>
-<title>MDC</title>
-<para></para>
-</sect1>
-
-
-</chapter>
-
-<chapter>
-<title>Frequently Asked Questions</title>
-
-<qandaset>
-
-<qandaentry>
-<question>
-<para>What are the installation requirements for log4j?</para>
-</question>
-<answer>
-<para>Log4j requires JDK 1.1.</para>
-</answer>
-</qandaentry>
-
-<qandaentry>
-<question id="faq-threadSafe">
-<para>Is log4j thread safe?</para>
-</question>
-<answer>
-<para>Yes it is.</para>
-</answer>
-</qandaentry>
-</qandaset>
-
-</chapter>
-
-&glo
-
-
+ <bookinfo>
+ <title>log4j manual</title>
+
+ <author>
+ <firstname>Ceki</firstname>
+ <surname>Gülcü</surname>
+ </author>
+
+ <author>
+ <firstname>Other authors</firstname>
+ <surname>as appropriate</surname>
+ </author>
+
+
+ <revhistory>
+ <revision>
+ <revnumber>v1.0</revnumber>
+ <date>2001-08-15</date>
+ <authorinitials>cgu</authorinitials>
+ </revision>
+ </revhistory>
+
+ <abstract>
+ <para>
+ This document describes the log4j API, its features and design
+ rationale. Log4j is an open source project based on the work of many
+ authors. It allows the developer to control which log statements are
+ output with arbitrary granularity. It is fully configurable at runtime
+ using external configuration files. Best of all, log4j has a gentle
+ learning curve. Beware: judging from user feedback, it is also quite
+ addictive.
+ </para>
+ </abstract>
+ </bookinfo>
+
+ &intro
+
+ <chapter>
+ <title>Architecture</title>
+ <para></para>
+
+ <sect1>
+ <title>Selecting</title>
+ <para></para>
+ </sect1>
+
+
+ <sect1>
+ <title>Directing Output</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>Formatting output</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>Object Renderers</title>
+ <para></para>
+ </sect1>
+
+
+ <sect1>
+ <title>Performance</title>
+ <para></para>
+ </sect1>
+
+ </chapter>
+
+
+ <chapter>
+ <title>Configuration</title>
+
+ <sect1>
+ <title>PropertyConfigurator</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>DOMConfigurator</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>Default configuration</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>Filters</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>Error handlers</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>Category Factories</title>
+ <para></para>
+ </sect1>
+
+ </chapter>
+
+ <chapter>
+ <title>Logging in servers and other Multithreaded environments</title>
+
+ <sect1>
+ <title>NDC</title>
+ <para></para>
+ </sect1>
+
+ <sect1>
+ <title>MDC</title>
+ <para></para>
+ </sect1>
+
+
+ </chapter>
+
+ <chapter>
+ <title>Frequently Asked Questions</title>
+
+ <qandaset>
+
+ <qandaentry>
+ <question>
+ <para>What are the installation requirements for log4j?</para>
+ </question>
+ <answer>
+ <para>Log4j requires JDK 1.1.</para>
+ </answer>
+ </qandaentry>
+
+ <qandaentry>
+ <question id="faq-threadSafe">
+ <para>Is log4j thread safe?</para>
+ </question>
+ <answer>
+ <para>Yes it is.</para>
+ </answer>
+ </qandaentry>
+ </qandaset>
+
+ </chapter>
+
+ &glo
+
</book>
1.33 +1 -1 jakarta-log4j/src/java/org/apache/log4j/Hierarchy.java
Index: Hierarchy.java
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/java/org/apache/log4j/Hierarchy.java,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- Hierarchy.java 2001/09/06 22:40:39 1.32
+++ Hierarchy.java 2001/09/08 15:46:14 1.33
@@ -122,7 +122,7 @@
public
void emitNoAppenderWarning(Category cat) {
// No appenders in hierarchy, warn user only once.
- if(this.emittedNoAppenderWarning) {
+ if(!this.emittedNoAppenderWarning) {
LogLog.error("No appenders could be found for logger (" +
cat.getName() + ").");
LogLog.error("Please initialize the log4j system properly.");
1.4 +0 -2 jakarta-log4j/src/sgml/intro.sgml
Index: intro.sgml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/sgml/intro.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- intro.sgml 2001/09/06 22:50:42 1.3
+++ intro.sgml 2001/09/08 15:46:14 1.4
@@ -42,7 +42,6 @@
<para>As Brian W. Kernigan and Rob Pike put it in their truly excellent
book <emphasis>"The Practice of Programming"</emphasis>
<blockquote>
-<literallayout>
As personal choice, we tend not to use debuggers beyond getting a
stack trace or the value of a variable or two. One reason is that it
is easy to get lost in details of complicated data structures and
@@ -54,7 +53,6 @@
the critical section of code, even assuming we know where that
is. More important, debugging statements stay with the program;
debugging sessions are transient.
-</literallayout>
</blockquote>
<para>Logging does have its drawbacks. It can slow down an application. If
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
