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: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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.
