logging-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rpo...@apache.org
Subject svn commit: r1476812 - in /logging/log4j/log4j2/trunk/src/site/xdoc/manual: eventlogging.xml flowtracing.xml markers.xml
Date Sun, 28 Apr 2013 18:40:20 GMT
Author: rpopma
Date: Sun Apr 28 18:40:20 2013
New Revision: 1476812

URL: http://svn.apache.org/r1476812
Log:
fixed spelling errors

Modified:
    logging/log4j/log4j2/trunk/src/site/xdoc/manual/eventlogging.xml
    logging/log4j/log4j2/trunk/src/site/xdoc/manual/flowtracing.xml
    logging/log4j/log4j2/trunk/src/site/xdoc/manual/markers.xml

Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/eventlogging.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/eventlogging.xml?rev=1476812&r1=1476811&r2=1476812&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/eventlogging.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/eventlogging.xml Sun Apr 28 18:40:20 2013
@@ -32,9 +32,9 @@
               Logging system, by itself it does not implement any of the features an audit
logging system would require
               such as guaranteed delivery.
             </p>
-            <p>The recommended way of using the EventLogger in a typcial web application
is to populate
+            <p>The recommended way of using the EventLogger in a typical web application
is to populate
               the ThreadContext Map with data that is related to the entire lifespan of the
request such as the user's
-              id, the user's ip address, the product name, etc. This can easily be done in
a servlet fileter where
+              id, the user's ip address, the product name, etc. This can easily be done in
a servlet filter where
               the ThreadContext Map can also be cleared at the end of the request. When an
event that needs to be
               recorded occurs a StructuredDataMessage should be created and populated.
               Then call EventLogger.logEvent(msg) where msg is a reference to the StructuredDataMessage.</p>

Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/flowtracing.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/flowtracing.xml?rev=1476812&r1=1476811&r2=1476812&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/flowtracing.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/flowtracing.xml Sun Apr 28 18:40:20 2013
@@ -39,7 +39,7 @@
             </p>
             <p>
               The two most used methods are the entry() and exit() methods. entry() should
be placed at the
-              beginning of methods, except perhaps ofr simple getters and setters. entry()
can be called
+              beginning of methods, except perhaps for simple getters and setters. entry()
can be called
               passing from 0 to 4 parameters. Typically these will be parameters passed to
the method.
               The entry() method logs with a level of TRACE and uses a Marker with a name
of "ENTER" which
               is also a "FLOW" Marker.

Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/markers.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/markers.xml?rev=1476812&r1=1476811&r2=1476812&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/markers.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/markers.xml Sun Apr 28 18:40:20 2013
@@ -58,7 +58,7 @@ public class MyApp {
         logger.entry(param);
 
         if (logger.isDebugEnabled()) {
-          logger.debug(UPDATE_MARKER, "UPDATE {} SET {}", table, formatCols);
+          logger.debug(UPDATE_MARKER, "UPDATE {} SET {}", table, formatCols());
 
         return logger.exit();
     }



Mime
View raw message