[
https://issues.apache.org/jira/browse/WICKET-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509568
]
Timo Rantalaiho commented on WICKET-254:
----------------------------------------
In fact there are some workarounds for some cases, e.g.
wicket.setParameterForNextRequest(dropDownChoice.getPageRelativePath(), new
Integer(index));
used to work on 1.3 before the fix, as discussed here
http://www.nabble.com/Unit-testing---updating-a-DropDownChoice-with-Ajax-tf3946499.html#a11300860
> Allow to set field values before submitting a form with Ajax in WicketTester
> ----------------------------------------------------------------------------
>
> Key: WICKET-254
> URL: https://issues.apache.org/jira/browse/WICKET-254
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta1, 1.3.0-beta2
> Environment: Ubuntu Dapper Linux, Sun java 1.5.0_10
> Reporter: Timo Rantalaiho
> Assignee: Jean-Baptiste Quenot
> Priority: Minor
> Fix For: 1.3.0-beta2
>
> Attachments: ajax-validation-sans-submit-1.3.0.zip,
> ajax-validation-sans-submit.zip, wicket-form-submit-enable-toggle.diff
>
>
> I have code to validate {{TextField}}s one by one with ajax. While the code
> works, I wasn't able to assert it working with WicketTester.
> The attached quickstart can be used to reproduce the problem on a 2.0
> snapshot. The code works in a browser (validity gets toggled true / false
> when changing the input length), but WicketTester fails.
> With WicketTester, the ajax event gets triggered (and it calls {{validate}}
> on the field), but {{isValid}} always returns {{true}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
