From 6aa9386d491938c0297265c67a6b4578998b86b8 Mon Sep 17 00:00:00 2001 From: Robert Burrell Donkin Date: Tue, 22 Jan 2002 22:10:45 +0000 Subject: [PATCH] Updated package documentation to reflect latest Log interface git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@138840 13f79535-47bb-0310-9956-ffa450edef68 --- src/java/org/apache/commons/logging/package.html | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/src/java/org/apache/commons/logging/package.html b/src/java/org/apache/commons/logging/package.html index 8a6954d..91fcd1b 100644 --- a/src/java/org/apache/commons/logging/package.html +++ b/src/java/org/apache/commons/logging/package.html @@ -14,7 +14,7 @@ prebuilt support for the following:

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 @@ prebuilt support for the following:

    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 @@ following algorithm is applied:

    throws away all logged output.
    • +

    Configuring the Underlying Logging System

    -

    Additionally, each individual Log implementation may +

    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.

    + +

    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 @@ component, consists of the following steps:

    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()).