[
https://issues.apache.org/jira/browse/WICKET-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998855#comment-12998855
]
Pedro Santos edited comment on WICKET-3471 at 2/24/11 2:16 PM:
---------------------------------------------------------------
Hi Martjin, iirc it was add because the core was failing in to refuse execute
behaviors in not enabled/disable behaviors. But it is fixed now and I'm 1+ to
bring this check responsibility back to core request processing. Initial
investigations shows that we can remove the checkUsability from clickLink and
executeAjaxEvent methods. Sending the patch with tests.
was (Author: pedrosans):
Hi Martjin, iirc it was add because the core was failing in to refuse
execute behaviors in not enabled/disable behaviors. But it is fixed now and I'm
1+ to bring this check responsibility back to core request processing. Initial
investigations shows that we can remove the checkUsability from clickLink and
executeAjaxEvent methods. Sending the patch with the tests.
> 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, 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
