Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 18504 invoked from network); 29 Jan 2008 21:48:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Jan 2008 21:48:39 -0000 Received: (qmail 74419 invoked by uid 500); 29 Jan 2008 21:48:23 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 74382 invoked by uid 500); 29 Jan 2008 21:48:23 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 74371 invoked by uid 500); 29 Jan 2008 21:48:23 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 74368 invoked by uid 99); 29 Jan 2008 21:48:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2008 13:48:23 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.130] (HELO eos.apache.org) (140.211.11.130) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2008 21:48:04 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 6E699D2D5 for ; Tue, 29 Jan 2008 21:48:11 +0000 (GMT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: tomcat-dev@jakarta.apache.org Date: Tue, 29 Jan 2008 21:48:11 -0000 Message-ID: <20080129214811.11967.2171@eos.apache.org> Subject: [Tomcat Wiki] Update of "FAQ/Logging" by tchize X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The following page has been changed by tchize: http://wiki.apache.org/tomcat/FAQ/Logging ------------------------------------------------------------------------------ The Servlet Specification requires Servlet Containers like Tomcat to provide at least a rudimentary implementation of the {{{ServletContext#log}}} method. Tomcat provides a much richer implementation than required by the Spec, as follows: * Prior to Tomcat 5.5, Tomcat provided a Logger element that you could configure and extend according to your needs. If you are using a Tomcat version previous to Tomcat 5.5, make sure to read the [http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html Logger configuration reference]. - * Starting with Tomcat 5.5, Logger was removed and [http://jakarta.apache.org/commons/logging Jakarta Commons-Logging] {{{Log}}} is used everywhere in Tomcat. Read the Commons-Logging documentation if you'd like to know how to better use and configure Tomcat's internal logging. + * Starting with Tomcat 5.5, Logger was removed and [http://jakarta.apache.org/commons/logging Jakarta Commons-Logging] {{{Log}}} is used everywhere in Tomcat. Read the Commons-Logging documentation if you'd like to know how to better use and configure Tomcat's internal logging. See also [http://tomcat.apache.org/tomcat-5.5-doc/logging.html] In addition, Tomcat does not swallow the System.out and System.err JVM output streams. You may use these streams for elementary logging if you wish, but a more robust approach such as commons-logging or [http://logging.apache.org/log4j Log4J] is recommended for production applications. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org