You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Lars Vonk (JIRA)" <ji...@apache.org> on 2008/08/02 10:29:44 UTC
[jira] Updated: (WICKET-1768) WicketTester dependant on order of
buttons being added with AjaxFallbackButton.setDefaultFormProcessing
[ https://issues.apache.org/jira/browse/WICKET-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Vonk updated WICKET-1768:
------------------------------
Attachment: quickstart.zip
> WicketTester dependant on order of buttons being added with AjaxFallbackButton.setDefaultFormProcessing
> -------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1768
> URL: https://issues.apache.org/jira/browse/WICKET-1768
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-M3
> Environment: winxp, jdk 1.5x
> Reporter: Lars Vonk
> Attachments: quickstart.zip
>
>
> I have a page with one form containing a radiogroup with one option and two AjaxFallbackButtons. One of the two buttons has its defaultFormProcessing set to false (because it does not need to submit the form). When I test the form submission with the FormTester the order in which I add the buttons to the form matter whether or not the selected radio choice is actually set on the model object or not. If I add the button with the defaulFormProcessing = false first is does not submit correctly, if I add it as last it does.
> This behavior only occurs with the FormTester and not in the real environment.
> I attached a quickstart project. In the test class FormTest you'll find a description how to replay the situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.