Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 19372 invoked from network); 23 Jan 2002 02:14:54 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 Jan 2002 02:14:54 -0000 Received: (qmail 27290 invoked by uid 97); 23 Jan 2002 02:15:00 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 27274 invoked by uid 97); 23 Jan 2002 02:15:00 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 27263 invoked by uid 97); 23 Jan 2002 02:14:59 -0000 Date: 22 Jan 2002 22:10:46 -0000 Message-ID: <20020122221046.46559.qmail@icarus.apache.org> From: rdonkin@apache.org To: jakarta-commons-cvs@apache.org Subject: cvs commit: jakarta-commons/logging/src/java/org/apache/commons/logging package.html X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N rdonkin 02/01/22 14:10:45 Modified: logging/src/java/org/apache/commons/logging package.html Log: Updated package documentation to reflect latest Log interface Revision Changes Path 1.4 +9 -7 jakarta-commons/logging/src/java/org/apache/commons/logging/package.html Index: package.html =================================================================== RCS file: /home/cvs/jakarta-commons/logging/src/java/org/apache/commons/logging/package.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- package.html 8 Jan 2002 21:35:10 -0000 1.3 +++ package.html 22 Jan 2002 22:10:45 -0000 1.4 @@ -14,7 +14,7 @@ JDK Logging API, included in JDK 1.4 or later systems. Each named Log instance is connected to a corresponding java.util.logging.Logger instance. -
  • LogKit from Apache's +
  • LogKit from Apache's Jakarta project. Each named Log instance is connected to a corresponding LogKit Logger.
  • NoOpLog implementation that simply swallows @@ -26,6 +26,8 @@

    Configuring the Logging Package APIs

    +

    Choosing A Log Implementation

    +

    The Logging Package APIs are configured based on the values of system properties, which are normally set on the command line that started your application. The following system properties are global to all @@ -49,8 +51,13 @@ throws away all logged output.

    • +

    Configuring the Underlying Logging System

    + +

    The basic principle is that the user is totally responsible for the +configuration of the underlying logging system. +Commons-logging should not change the existing configuration.

    -

    Additionally, each individual Log implementation may +

    Each individual Log implementation may support its own configuration properties. These will be documented in the class descriptions for the corresponding implementation class.

    @@ -72,11 +79,6 @@ references to multiple loggers that are used for different purposes. A typical scenario for a server application is to have each major component of the server use its own Log instance. -
  • Optionally, you can dynamically change the logging detail level by - calling Log.setLevel() with - an appropriate constant from the Log interface. Note that, - in most cases, the underlying logging system configuration will have - been preconfigured by the system administrator.
  • Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (debug(), info(), warn(), error, and fatal()).
    • -- To unsubscribe, e-mail: For additional commands, e-mail: