[
https://issues.apache.org/jira/browse/WICKET-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mathilde Pellerin updated WICKET-3711:
--------------------------------------
Attachment: quickstart_FormTesterIssue.tar.gz
In attachment, you will find a quickstart which reproduce the problem that I
had about wicketTester and error messages. Follow the link above to see
discussion about this problem on mailing list :
http://markmail.org/message/vkaoprbbnp5gjzb4
> FormTester doesn't treat SubmitLink and AjaxSubmitLink correctly
> ----------------------------------------------------------------
>
> Key: WICKET-3711
> URL: https://issues.apache.org/jira/browse/WICKET-3711
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.4.17, 1.4.18
> Reporter: Carl-Eric Menzel
> Attachments: 0001-added-test-for-FormTester-SubmitLink-problem.patch,
> 0001-added-test-for-FormTester-SubmitLink-problem.patch,
> 0002-fix-formtester-not-providing-correct-form-request-pa.patch,
> 0002-fix-formtester-not-providing-correct-form-request-pa.patch,
> 0003-fixed-ajaxsubmitlink-testing.-hackish.patch,
> 0003-fixed-ajaxsubmitlink-testing.-hackish.patch,
> quickstart_FormTesterIssue.tar.gz
>
>
> We ran into a testing issue with FormTester. When using a SubmitLink or
> AjaxSubmitLink it does not properly collect and use the values for the
> various form fields. The problem appears to be with a very inconsistent
> handling of "parametersForNextRequest" and MockServletRequest's parameter
> map. I did not completely manage to take it apart, frankly, it's a mess. I
> have a set of patches against 1.4.17 that introduce a test for this and also
> fix the problem. The fix is a bit hackish, but it works and does not break
> anything else.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
