You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Jorg Heymans <jh...@domek.be> on 2003/11/13 17:37:49 UTC
nested diagnostic contexts and cocoon
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
Re: nested diagnostic contexts and cocoon
Posted by Joerg Heinicke <jh...@virbus.de>.
On 15.11.2003 10:01, Jorg Heymans wrote:
> I checked the dev list, it seems that this is a rather new feature that
> was put on the 2.1 branch and not 2.04?
Exactly, only 2.1.
> I was hoping for a clear-cut
> solution but by the looks it's too early for this :)
Unfortunately yes.
Joerg
> Joerg Heinicke wrote:
>
>> On 13.11.2003 17:37, Jorg Heymans wrote:
>>
>>> 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
>>
>>
>>
>> Have you searched for threads about log4j of the last 2 months? The
>> complete core logging was refactored in the sense of the possibility
>> of easily replacing logkit:
>> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106321926824665&w=2.
>> It's only somebody missing who does the work ;-)
>>
>> Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: nested diagnostic contexts and cocoon
Posted by Jorg Heymans <jh...@domek.be>.
I checked the dev list, it seems that this is a rather new feature that
was put on the 2.1 branch and not 2.04? I was hoping for a clear-cut
solution but by the looks it's too early for this :)
tnx
Jorg
Joerg Heinicke wrote:
> On 13.11.2003 17:37, Jorg Heymans wrote:
>
>> 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
>
>
> Have you searched for threads about log4j of the last 2 months? The
> complete core logging was refactored in the sense of the possibility of
> easily replacing logkit:
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106321926824665&w=2.
> It's only somebody missing who does the work ;-)
>
> Joerg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: nested diagnostic contexts and cocoon
Posted by Joerg Heinicke <jh...@virbus.de>.
On 13.11.2003 17:37, Jorg Heymans wrote:
> 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
Have you searched for threads about log4j of the last 2 months? The
complete core logging was refactored in the sense of the possibility of
easily replacing logkit:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106321926824665&w=2.
It's only somebody missing who does the work ;-)
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org