[
https://issues.apache.org/jira/browse/WICKET-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Laframboise updated WICKET-4801:
--------------------------------------
Attachment: WICKET-4801-quickstart.zip
> BaseWicketTester.executeAjaxEvent only fires one of multiple behaviors bound
> to a given event
> ---------------------------------------------------------------------------------------------
>
> Key: WICKET-4801
> URL: https://issues.apache.org/jira/browse/WICKET-4801
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0
> Reporter: Brian Laframboise
> Attachments: WICKET-4801-quickstart.zip
>
>
> Migrating from Wicket 1.4.21 to 6.0.0, I have a test failing because an
> AjaxFormComponentUpdatingBehavior was not executed despite calling
> WicketTester.executeAjaxEvent on the desired component with the correct event.
> The component in question has two behaviors added to it; both behaviors are
> bound to the same event. My test is only interested in exercising one of the
> behaviors.
> The root cause appears to be that BaseWicketTester uses
> WicketTesterHelper.findAjaxEventBehaviour to find and execute a behavior.
> That method returns only the first behavior matching the given event - even
> though there can be many.
> From what I can gather, Wicket 1.4.21 happens to find the behaviour I'm
> interested in whereas Wicket 6.0.0 happens to find the other one.
> When I exercise the same code in an actual servlet environment (Jetty), both
> behaviors are executed as expected.
> I've attached a quickstart project with a test case that reproduces this
> issue.
--
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
