Found the bug.
Will be in RC3
On Thu, Mar 24, 2011 at 9:31 PM, Igor Vaynberg wrote:
> probably an oversight of all the refactory. jira issue please.
>
> -igor
>
>
> On Thu, Mar 24, 2011 at 12:48 PM, Jens Zastrow
> wrote:
> > Enabling with getRequestLoggerSettings().setRequestLoggerEnabled(true)
probably an oversight of all the refactory. jira issue please.
-igor
On Thu, Mar 24, 2011 at 12:48 PM, Jens Zastrow wrote:
> Enabling with getRequestLoggerSettings().setRequestLoggerEnabled(true)
> doesnt show any requests.
>
> Seems that the Application.logEventTarget and Application.logRespon
Put a breakpoint at org.apache.wicket.Application.getRequestLogger() and see
what happens
On Thu, Mar 24, 2011 at 8:48 PM, Jens Zastrow wrote:
> Enabling with getRequestLoggerSettings().setRequestLoggerEnabled(true)
> doesnt show any requests.
>
> Seems that the Application.logEventTarget and A
Enabling with getRequestLoggerSettings().setRequestLoggerEnabled(true)
doesnt show any requests.
Seems that the Application.logEventTarget and
Application.logResponseTarget are never invoked at all from the
wicket-core,
nevertheless the get overridden in WebApplication???
Any hints?
---
