Return-Path: X-Original-To: apmail-logging-commits-archive@minotaur.apache.org Delivered-To: apmail-logging-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 621BDCF7A for ; Sat, 26 May 2012 15:39:17 +0000 (UTC) Received: (qmail 28898 invoked by uid 500); 26 May 2012 15:39:17 -0000 Delivered-To: apmail-logging-commits-archive@logging.apache.org Received: (qmail 28871 invoked by uid 500); 26 May 2012 15:39:17 -0000 Mailing-List: contact commits-help@logging.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@logging.apache.org Delivered-To: mailing list commits@logging.apache.org Received: (qmail 28864 invoked by uid 99); 26 May 2012 15:39:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 15:39:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 15:39:14 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id A797F238896F; Sat, 26 May 2012 15:38:52 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1342915 - in /logging/log4j/trunk/src: changes/changes.xml site/fml/faq.fml Date: Sat, 26 May 2012 15:38:52 -0000 To: commits@logging.apache.org From: ggregory@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120526153852.A797F238896F@eris.apache.org> Author: ggregory Date: Sat May 26 15:38:52 2012 New Revision: 1342915 URL: http://svn.apache.org/viewvc?rev=1342915&view=rev Log: Bugzilla [52424]: Misspelled words in FAQ. Fix other misspellings too. Modified: logging/log4j/trunk/src/changes/changes.xml logging/log4j/trunk/src/site/fml/faq.fml Modified: logging/log4j/trunk/src/changes/changes.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/changes/changes.xml?rev=1342915&r1=1342914&r2=1342915&view=diff ============================================================================== --- logging/log4j/trunk/src/changes/changes.xml (original) +++ logging/log4j/trunk/src/changes/changes.xml Sat May 26 15:38:52 2012 @@ -21,6 +21,7 @@ + Misspelled words in FAQ. Fix one BZ number in Changelog of 1.2.16. Missing comma in class header Javadoc for Level. Log4J SyslogAppender does not handle the TAG field. Modified: logging/log4j/trunk/src/site/fml/faq.fml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/site/fml/faq.fml?rev=1342915&r1=1342914&r2=1342915&view=diff ============================================================================== --- logging/log4j/trunk/src/site/fml/faq.fml (original) +++ logging/log4j/trunk/src/site/fml/faq.fml Sat May 26 15:38:52 2012 @@ -108,7 +108,7 @@

log4j is based on a named logger hierarchy.

log4j is fail-stop. However, altough it certainly +

log4j is fail-stop. However, although it certainly strives to ensure delivery, log4j does not guarantee that each log statement will be delivered to its destination.

@@ -189,7 +189,7 @@ 262 [main] DEBUG SortAlgo.OUTER i=1 - Outer loop. 276 [main] DEBUG SortAlgo.SWAP i=1 j=0 - Swapping intArray[0] = 1 and intArray[1] = 0 290 [main] DEBUG SortAlgo.OUTER i=0 - Outer loop. -304 [main] INFO SortAlgo.DUMP - Dump of interger array: +304 [main] INFO SortAlgo.DUMP - Dump of integer array: 317 [main] INFO SortAlgo.DUMP - Element [0] = 0 331 [main] INFO SortAlgo.DUMP - Element [1] = 1 343 [main] INFO examples.Sort - The next log statement should be an error message. @@ -224,7 +224,7 @@ application.

The open and collaborative way in which log4j is developped +

The open and collaborative way in which log4j is developed ensures that it continues to preserve and even widen its competitive edge. At some point, input from bright developers from all over the world is bound to make a difference. @@ -236,7 +236,7 @@ What are Loggers? -

Lggers lie at the heart of log4j. Loggers define a hierarchy and give +

Loggers lie at the heart of log4j. Loggers define a hierarchy and give the programmer run-time control on which statements are printed or not.

@@ -477,7 +477,7 @@ public class Foo { NTEventLogAppender? -

Unfotunately, the logger names are hardcoded within the +

Unfortunately, the logger names are hardcoded within the message resource DLL (see previous question about NTEventLogAppender), so there isn't any easy way to override those dynamically... in fact, I don't think it's possible to @@ -545,7 +545,7 @@ public class Foo { there a method to remove logger instances?

It is quite nontrivial to define the semantics of a - "removed" logger escecially if it is still referenced by the + "removed" logger especially if it is still referenced by the user. Future releases may include a remove method in the Logger class.

@@ -562,7 +562,7 @@ public class Foo {

- How about the timesamps of events generated by multiple + How about the timestamps of events generated by multiple processes across multiple hosts (possibly across multiple timezones)? @@ -577,7 +577,7 @@ public class Foo {

Timestamps are stored in UTC format inside the event. Consequently, when displayed or written to a log file, timestamps appear in the same timezone as the host displaying - or creating the logfile. Note that because the clocks of + or creating the log file. Note that because the clocks of various machines may not be synchronized, there may be timestamp inconsistencies between events generated on different hosts. The EnhancedPatternLayout in the extras companion @@ -589,14 +589,14 @@ public class Foo { Why can't log4j find my properties file in a J2EE or WAR application?

The short answer: the log4j classes and the properties file - are not within the scope of the same classloader. + are not within the scope of the same class loader.

The long answer (and what to do about it): J2EE or Servlet containers utilize Java's class loading system. Sun changed - the way classloading works with the release of Java 2. In - Java 2, classloaders are arranged in a hierarchial - parent-child relationship. When a child classloader needs to + the way class loading works with the release of Java 2. In + Java 2, class loaders are arranged in a hierarchical + parent-child relationship. When a child class loader needs to find a class or a resource, it first delegates the request to the parent.

@@ -623,7 +623,7 @@ public class Foo {

Because the configureAndWatch launches a - separate wathdog thread, and because there is no way to stop + separate watchdog thread, and because there is no way to stop this thread in log4j 1.2, the configureAndWatch method is unsafe for use in J2EE envrironments where applications are recycled.