On Jun 28, 2005, at 7:18 PM, Dave wrote:
I tried
<logger name ="org.apache.log4j/>
<level value ="off"/>
<logger/>
I'm using 1.3.0alpha6 in WSAD
This gets rid of the statements below generated internally starting
with
DEBUG
I need to get rid of the log4j:INFO stuff
is there any way?
I was working on this yesterday to get the log4j 1.2 tests passing
against log4j 1.3 and the stray internal log messages mess up the
comparisons. I will try to commit a fix tomorrow. Unfortunately,
you can't currently bypass the logging within the Joran configurator
at the moment since it will have already logged before you are able
to turn it off.
There are a couple complications, one is that the "internal" logs use
loggers descendent from "org.apache.log4j", however the same loggers
are also used within the unit tests. The log4j 1.3 tests have added
configuration lines to turn off specific loggers (like
org.apache.log4j.FileAppender) that corrupt the test expectations.
The log4j 1.2 tests don't (and shouldn't) have to employ tricks to
get consistent behavior. In my current patch, I've changed the log
names for the internal loggers to "log4j-internal." + class name.
The other change was to have the configurators initialize "log4j-
internal" with its additivity is set to false, its threshold to INFO
or DEBUG depending of the value of the configurations debug attribute
and attached to a console appender. This should mimic the log4j 1.2
behavior or at least close enough so that internal logging doesn't
mess up the tests. I'm not sure if that is where we will end up, but
it at least should be a step in the right direction.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
