Re: not sure if this is a bug.

[Peter Donald <pe...@realityforge.org>]

Do you actually need to setup Log4j separately? environment.xml will configure 
the hierarchy you use. 

Is there any reason you can choose just to remove the line;

PropertyConfigurator.configure("log4j.properties") 

??

On Thu, 27 Mar 2003 12:50, Korosh Afshar wrote:
> 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: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org

-- 
Cheers,

Peter Donald
----------------------------------------
Whatever you do will be insignificant, 
but it is very important that you do it. 
                              --Gandhi
---------------------------------------- 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org