At 06:05 PM 2/23/2005, you wrote:
Martin,
Others can chime in here, but my personal opinion is that it is a bad idea
to include configuration files as part of jar files and changing the default
behavior. The configuration of the log4j, what appenders are created, what
logger messages are sent to where, all of that should be completely at the
control of the user deploying the application. Anything that is added that
short circuits or changes expected, normal behavior in this area is not
good. I want to KNOW that the log4j.xml file that I have in my container or
in my web app (in the case of child-first classloading) will be used, not
something from a jar file that I happened to include. And given some of the
recent discussion about classloader issues with JCL, putting more behavior
around this might not be the greatest thing to do.
Well put, Mark.
That being said, it might be interesting to explore having the
initialization behavior configurable. But, again my opinion, it would have
to be done in a way where it requires explicit effort on the part of the
developer/deployer to setup and override. No guess work.
:-)
-Mark
--
Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
