It is "the Complete Log4j Manual" for as of v1.2.9, Dec, 2004, Page 68,
there is "<root> element" bullet at the bottom of the page.

Note that it says "Similar to the <logger> element, declaring <root> element
will have the effect...". So it is not an exception for <root> element.

And yes, I tried with v1.2.8, and it seems to do what this quote says. In
1.3, the behavior is different.

Regards
Sergiu

-----Original Message-----
From: Curt Arnold [mailto:[EMAIL PROTECTED] 
Sent: February 23, 2007 12:38 AM
To: Log4J Users List
Subject: Re: Root logger appenders in log4j 1.3


On Feb 22, 2007, at 11:15 PM, Jacob Kjome wrote:

>
> That's an interesting quote.  I have to admit that I haven't read  
> the Log4j manual and that's new to me.  In Log4j, reconfigurations  
> are genrally not destructive.  They are cumulative.  It sounds like  
> the manual is claiming that the ROOT logger is an exception to the  
> rule.
>
> Have you tried this with Log4j-1.2.xx?  Do you get the same results  
> or do you get the behavior described in the manual?  It's certainly  
> possible that this contract was broken in 1.3.
>
> Ceki, Curt, anyone, can you shed any light on this topic?  What's  
> the expected behavior?  Is the manual right, wrong, or just being  
> misinterpreted?
>
>
> Jake
>

My initial take was the same as yours.  The quote from "the manual"  
sounds incorrect but it is not in context.  I assume that they mean  
Ceki's "The complete log4j manual", but the don't specify precisely  
what "manual" they are referencing and a detailed reference would be  
handy.  I have an old beat up paperback copy, but didn't buy an  
electronic edition and the text may have been added in subsequent  
editions.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to