logging-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rgo...@apache.org
Subject svn commit: r1479698 - /logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm
Date Mon, 06 May 2013 20:26:38 GMT
Author: rgoers
Date: Mon May  6 20:25:02 2013
New Revision: 1479698

URL: http://svn.apache.org/r1479698
Log:
Reword paragraph that looks too similar to Logback's doc

Modified:
    logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm

Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm?rev=1479698&r1=1479697&r2=1479698&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm Mon May  6 20:25:02
2013
@@ -131,15 +131,17 @@ public class Bar {
 }</pre>
           </p>
           <p>
-            If no configuration files are present log4j will default to the DefaultConfiguration
which
-            will set up a minimal logging environment consisting of a
-            <a href="../log4j-core/apidocs/org/apache/logging/log4j/core/appender/ConsoleAppender.html">ConsoleAppender</a>
-            attached to the root logger. The output will be formatted using a
-            <a href="../log4j-core/apidocs/org/apache/logging/log4j/core/layout/PatternLayout.html">PatternLayout</a>
-            set to the pattern "%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n".
+            Log4j will provide a default configuration if it cannot locate a configuration
file. The default
+            configuration, provided in the DefaultConfiguration class, will set up:
+            <ul>
+              <li>A <a href="../log4j-core/apidocs/org/apache/logging/log4j/core/appender/ConsoleAppender.html">ConsoleAppender</a>
+                attached to the root logger.</li>
+              <li>A <a href="../log4j-core/apidocs/org/apache/logging/log4j/core/layout/PatternLayout.html">PatternLayout</a>
+                set to the pattern "%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"
attached to the ConsoleAppender</li>
+            </ul>
           </p>
           <p>
-            Note that by default, the root logger is assigned to <code>Level.ERROR</code>.
+            Note that by default Log4j assigns the root logger to <code>Level.ERROR</code>.
           </p>
           <p>The output of MyApp would be similar to:
 <pre class="prettyprint linenums">
@@ -271,24 +273,24 @@ public class Bar {
         <a name="AdvertisingAppenderConfigurations"/>
         <subsection name="Advertising Appender Configurations">
           <p>
-            Log4j provides the ability to expose appender configurations to external systems
when the 'advertiser' 
+            Log4j provides the ability to expose appender configurations to external systems
when the 'advertiser'
             attribute of the configuration element has been specified.  Advertisement is
enabled for individual appenders by setting
             the 'advertise' attribute of the appender to 'true'.
           </p>
           <p>
             Log4j currently provides one Advertiser implementation: a Multicast DNS advertiser,
which can be used to retrieve and parse
-            a log file or process events from a socket-based appender.  Additional Advetiser
implementations could be 
-            written which leverage other mechanisms for exposing the appender configuration
- for example, by exposing the 
+            a log file or process events from a socket-based appender.  Additional Advetiser
implementations could be
+            written which leverage other mechanisms for exposing the appender configuration
- for example, by exposing the
             configuration via JMX or storing it in a database.
           </p>
           <p>
-            Chainsaw supports discovery of the Multicast DNS-exposed appender configurations
for file-based and socket-based appenders.  When 
-            Chainsaw discovers an advertised appender, Chainsaw will display an entry for
the appender in the 'ZeroConf' screen, and the user can 
+            Chainsaw supports discovery of the Multicast DNS-exposed appender configurations
for file-based and socket-based appenders.  When
+            Chainsaw discovers an advertised appender, Chainsaw will display an entry for
the appender in the 'ZeroConf' screen, and the user can
             double-click on the entry in order to begin receiving events generated by that
appender, with no further user configuration required.
           </p>
           <p>
             Note that individual appenders may require that additional information provided
in the appender configuration.  For example,
-            a FileAppender must specify an advertiseURI which can be used to retrieve the
file contents. 
+            a FileAppender must specify an advertiseURI which can be used to retrieve the
file contents.
             file://, http:// and Apache Commons VFS-supported URIs are all supported by Chainsaw.
           </p>
           <pre class="prettyprint linenums"><![CDATA[



Mime
View raw message