I would tend to have a minimal log4j.xml containing basic configuration for
the root logger, which I usually set to "WARN" to avoid being bombarded with
annoying messages from libraries I don't care about. However, there is no
necessity to have a log4j.xml (or log4j.properties). Log4j can be configured
via config file or programmatically (or both), but if Log4j can't find any
config file, it will say as much in System.err, which I generally try to
avoid.
All the other stuff can be configured programmatically as Bender suggested.
Jake
On Tue, 2 Nov 2010 14:46:52 +0100
Bender Heri <hben...@ergonomics.ch> wrote:
I don't know. You have to try if the log4j.xml can be omitted.
Heri
-----Original Message-----
From: Mohan.Radhakrishnan [mailto:moh...@fss.co.in]
Sent: Tuesday, November 02, 2010 2:39 PM
To: log4j-user@logging.apache.org
Subject: RE: Extending Logger
Yes. I am responding to your suggestion.
The setup performance is not very important. The runtime performance though
is. If I setup everything programmatically log4j.xml is not at all needed ?
--
View this message in context:
http://old.nabble.com/Extending-Logger-tp30018462p30113852.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
