You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2011/06/23 17:51:47 UTC

[jira] [Updated] (WICKET-3832) RequestLogger doesn't log incoming event and outgoing page

     [ https://issues.apache.org/jira/browse/WICKET-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Dashorst updated WICKET-3832:
-------------------------------------

    Description: 
The requestlogger currently doesn't log the incoming request and the outgoing page, which it did in 1.4.x (and earlier). This is due to

getRequestLogger().logEventTarget(handler);
getRequestLogger().logResponseTarget(handler);

not being called. This results in log entries like:

[2011-06-22 11:43:20,836] [TP-Processor6] RequestLogger | time=12,event=null,response=null,sessioninfo=...

which isn't saying much, and making every presentation I gave on the RequestLogger, and chapter 14 from WiA look foolish :)


  was:
The requestlogger currently doesn't log the incoming request and the outgoing page, which it did in 1.4.x (and earlier). This is due to

getRequestLogger().logEventTarget(handler);
getRequestLogger().logResponseTarget(handler);

not being called.


> RequestLogger doesn't log incoming event and outgoing page
> ----------------------------------------------------------
>
>                 Key: WICKET-3832
>                 URL: https://issues.apache.org/jira/browse/WICKET-3832
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.5-RC4
>            Reporter: Martijn Dashorst
>
> The requestlogger currently doesn't log the incoming request and the outgoing page, which it did in 1.4.x (and earlier). This is due to
> getRequestLogger().logEventTarget(handler);
> getRequestLogger().logResponseTarget(handler);
> not being called. This results in log entries like:
> [2011-06-22 11:43:20,836] [TP-Processor6] RequestLogger | time=12,event=null,response=null,sessioninfo=...
> which isn't saying much, and making every presentation I gave on the RequestLogger, and chapter 14 from WiA look foolish :)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira