I ended up with a custom RequestCycle
@Override
public boolean processRequestAndDetach() {
boolean result;
try {
result = processRequest();
} finally {
detach();
}
popMDC();
return result;
}
@Override
protected void onBeginRequest()
{
pushMDC();
}
François
Le 18 févr. 2016 à 08:17, Martin Grigorov <[email protected]> a écrit :
> Hi Francois,
>
> You can create a custom RequestLogger that just calls
> super.performLogging() and pops the context.
> Setup it with org.apache.wicket.Application#newRequestLogger()
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Feb 17, 2016 at 2:34 PM, Francois Meillet <
> [email protected]> wrote:
>
>> Dear All,
>>
>> I use the Mapped Diagnostic Context concept
>> https://logging.apache.org/log4j/2.x/manual/thread-context.html).
>>
>> Using log4j 2.x and a specific AbstractRequestCycleListener,
>> I overrided onBeginRequest() to perform a ThreadContext.push(id)
>> and onDetach(RequestCycle cycle) to perform a ThreadContext.pop();.
>>
>> So far so good for all the logs but the IRequestLogger's logs.
>>
>> I notice that the IRequestLogger # performLogging() is called after the
>> RequestCycle # onDetach() has been called.
>>
>> I would like it to happen before !
>> Is that possible ?
>>
>>
>> François
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
