[
https://issues.apache.org/jira/browse/WICKET-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Dashorst resolved WICKET-3832.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC6
There were a couple more issues with the request logger implementation. It used
getPage() to log the page class and page id: causing page instantiations at
wrong times. This has been remedied by requiring an extra method to provide the
page id (if present). The page instantiation caused problems with the
Swarm/Wasp security framework.
Further more the request logger now logs the requested URL as well.
> 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
> Fix For: 1.5-RC6
>
> Attachments: wicket-3832.patch
>
>
> 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
