[
https://issues.apache.org/jira/browse/WICKET-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053933#comment-13053933
]
Martijn Dashorst edited comment on WICKET-3832 at 6/23/11 3:50 PM:
-------------------------------------------------------------------
I'd like to solve this issue, but the handlers are a bit opaque for me as to
how they relate to events and responses. Giving pointers on where to hook into
Wicket would be awesome. I'm currently toying with RequestCycleListener, but
not sure if that will solve my issues.
was (Author: dashorst):
I'd like to solve this issue, but the handlers are a bit opaque for me as
to how they relate to events and responses.
> 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
