[
https://issues.apache.org/jira/browse/WICKET-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998847#comment-12998847
]
Martijn Dashorst commented on WICKET-3471:
------------------------------------------
*The* big question in my opinion is why doesn't Wicket throw an exception from
inside core when an invisible/disabled component receives an event during
wickettester processing? Why is that checkUsability necessary?
> WicketTester checkUsability is called before the request has started
> --------------------------------------------------------------------
>
> Key: WICKET-3471
> URL: https://issues.apache.org/jira/browse/WICKET-3471
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.15
> Reporter: Emond Papegaaij
> Attachments: WICKET-3471.patch, quickstart.tar.bz2
>
>
> For example, when clicking a link, the checkUsability method is called with
> the link before RequestCycle.onBeginRequest has been called. This causes
> tests to fail when, for example, the link has a security check that requires
> the request cycle. I've created a quickstart that demonstrates the problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
