Thanks guys,
This makes it a lot more clear, and indeed gives a an explanation to the
behauvior I was getting.
I will change small things in my NDC usage, such that it will work fine to
track the servlets.
Thanks,
Eddie :)
>From: "Mark Masterson" <[EMAIL PROTECTED]>
>Reply-To: "LOG4J Users Mailing List" <[EMAIL PROTECTED]>
>To: "LOG4J Users Mailing List" <[EMAIL PROTECTED]>
>Subject: RE: NDC usage ?? -> some help please ? >> Hellu
>Date: Mon, 11 Jun 2001 21:11:21 +0200
>
>Eddie,
>
>Nobody's probably jumping to answer your more general question because the
>NDC mechanism is very flexible - it is impossible to say "this is THE right
>way to use it", simply because there are so many different ways that you
>could use it, for many different purposes. Having said that, the answer to
>your newer question is more straightforward (which is why you're getting
>more than one answer!). NDC follows the thread of execution: in your
>example, because you call your second class from the servlet, the thread of
>execution moves from your servlet to your other class, and the NDC stack is
>built to reflect this. In this way, it's just like the standard Java
>execution stack. Different servlets, OTOH == different threads ==
>different
>NDC stacks. Do you understand?
>
>Thus, the answer to (part) of your original question is: no, the NDC is not
>bound to any specific Category instance. It's bound to the thread of
>execution that pushes the first item onto its stack. Once you understand
>this, the answers to the rest of your questions (which are *very* dependent
>on the details of your own code) are usually fairly self-evident.
>
>Cheers,
>Mark
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
