You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Rob Audenaerde (JIRA)" <ji...@apache.org> on 2013/01/09 13:12:12 UTC
[jira] [Created] (WICKET-4960) Easier logging of UI interactions
Rob Audenaerde created WICKET-4960:
--------------------------------------
Summary: Easier logging of UI interactions
Key: WICKET-4960
URL: https://issues.apache.org/jira/browse/WICKET-4960
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 6.4.0
Reporter: Rob Audenaerde
Priority: Minor
As developer I wish to log all the user activity in my wicket application, so that I can use this information to trace error, generate tests and logs. (See also http://stackoverflow.com/questions/14094755/logging-user-actions-in-wicket)
Currently, this can be achieved by either:
- subclassing all UI components and handle their: onSubmits, onClicks, onChanged() ... etc. It is impossible for BookmarkablePageLinks and easier for Ajax components (especially when using the onEvent since Wicket 1.5).
- attaching a logging behaviour and try to do something with the onRequest()
- AOP and create intersections on the methods above.
What I would really like is a Behavior that can be attached to components that can intercept/log the user interactions. Currently this is impossible, so it would require some rewriting.
The main benefits would be the logging. If the logging is of a consistent format, I think it could also be used to drive the WicketTester, making creating tests a lot easier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira