[
https://issues.apache.org/jira/browse/WICKET-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054321#comment-13054321
]
Martijn Dashorst commented on WICKET-3832:
------------------------------------------
My issue is identifying the page that was the target of the incoming event, and
the page that was rendered as the final response. This way we have 1.4 parity
in functionality.
I agree that we should strive to improve our request logging and exposing more
detail. What we are more interested in rather than the guts is how long the
event part took and how long the rendering part. So from the start of the
request until the end of onClick for example, and from the end of onClick to
the end of request. That would make identifying the slow pages/requests much
easier. Now it is hard to discern whether the event handler was slow or the
page construction/rendering.
> 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
