Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3FB4971B.70601@domek.be>
Date: Fri, 14 Nov 2003 09:49:31 +0100
From: Jorg Heymans <jh@domek.be>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20031013 Thunderbird/0.3
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: nested diagnostic contexts (log4j) and cocoon
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Maybe this topic was too advanced for the users-list so I'm reposting it 
here.

In short: anyone familiar with NDC in log4j knows how to get a similar 
concept running in cocoon using logkit? In the generator i would do a 
NDC.push("identstring") and in the serializer a NDC.remove().

Hope this question is clear enough now.

tnx
Jorg

-------- Original Message --------
Subject: nested diagnostic contexts and cocoon
Date: Thu, 13 Nov 2003 17:37:49 +0100
From: Jorg Heymans <jh@domek.be>
Reply-To: users@cocoon.apache.org
To: users@cocoon.apache.org

Hi,

Is there any way of using log4j-alike NDC's in the cocoon 2.04 logging
mechanism? I need to be able to make coherent logging output of an
execution path that consists of multiple pipelines, transformers (both
custom and standard), and this under high load?

With log4j, you would push an identifying string onto the logging
framework at the entry point of the application. Subsequent logging
output (within the same thread?) would then have this string prepended
in the output as well, at the exit point (ie request done) you would pop
this string off again.

Is similar stuff possible in cocoon? I would rather not incorporate
log4j unless it's very easy to do

thoughts?
Jorg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org