if you have an avalon-phoenix SAR applicaiton, that uses LogEnabled
with Logger interace and seperately
PropertyConfigurator.configure("log4j.properties"), then the
PropertyConfiguraotr.configure overwrites paramerters loaded using the
phoenix container.
so that if e.g. you configured avalon logger with log4j using
environment.xml and also explicitly loaded log4j.properties using
PropertyConfigurator then second time around, your log4j.properties
attributes overwrite whatever log4j tags attributres you defined in your
environment.xml.
This situation arises when there is a need to maintain log4j logging
scheme because e.g. some legacy code takes log4j Logger as constructor.
This forces you to configure Log4j and pass into your legacy code
constructor.
Not sure if this can be considered a bug since this is a special case
where to use legacy code I need to setup log4j Logger specificaly.
regards
K.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
