You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2008/04/02 22:03:27 UTC
[jira] Updated: (WICKET-1291) WicketTester Doesn't Support
setDefaultFormProcessing(false)
[ https://issues.apache.org/jira/browse/WICKET-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1291:
---------------------------------------
Fix Version/s: (was: 1.3.3)
1.3.4
> WicketTester Doesn't Support setDefaultFormProcessing(false)
> ------------------------------------------------------------
>
> Key: WICKET-1291
> URL: https://issues.apache.org/jira/browse/WICKET-1291
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-final
> Reporter: Brandon Fuller
> Assignee: Maurice Marrink
> Priority: Minor
> Fix For: 1.3.4
>
>
> I was trying to use the WicketTester to click the button for an AjaxFallbackButton that has setDefaultFormProcessing(false). So I wanted to execute the onclick for the component, like this:
> tester.executeAjaxEvent("meetingForm:inputForm:rootViewPanel:addOrganization", "onclick");
> What seems to happen is that the pages tries to update all the form fields and perform validation. This is incorrect in the context for the setDefaultFormProcessing(false) behavior.
> I was looking at the source for BaseWicketTester and noticed that in executeAjaxEvent(), it always tries to submit the form if the behavior is a AjaxFormSubmitBehavior. This wouldn't be correct in the case of when you set setDefaultFormProcessing(false) on the button. I think it needs to check for setDefaultFormProcessing at that point.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.