Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Date: 24 Mar 2003 15:36:25 -0000
Message-ID: <20030324153625.27396.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: axis-dev@ws.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 18281] New:  -
    log4j default configuration might be too aggressive

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18281>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18281

log4j default configuration might be too aggressive

           Summary: log4j default configuration might be too aggressive
           Product: Axis
           Version: current (nightly)
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: heiko@schlund.de


axis comes with a "log4j.properties" configuration file.
in this default configuration the "log4j.rootCategory" is set.

this changes the general behaviour for use of log4j (also external to axis).
(my concrete problem: since using axis, i get lots and lots of output to console
which i do not want there, but solely in log-files)

i propose changing this:
"log4j.rootCategory=INFO, CONSOLE"

to something like this:
"log4j.category.org.apache.axis = INFO, CONSOLE".

at least this way, the logging behaviour of external projects would not be
altered by simply using axis.

disclaimer: i do not think i fully understand log4j, i might be entirely
confused. and/or there could be a nicer solution to the problem i have.

but overriding the log4j configuration (as proposed on
http://docs.pushtotest.com/axisdocs/developers-guide.html) that comes
(implicitely) when using axis is problematic, since this (default
log4j-)configuration already happens when the classloader finds log4j, as i
understand it - setting System-properties in regular code is already too late.