[
https://issues.apache.org/jira/browse/WICKET-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490701#comment-13490701
]
Stijn de Witt commented on WICKET-1826:
---------------------------------------
I can confirm this issue is present in Wicket 1.4.21.
I am a bit surprised by the Minor priority of this issue, as this case doesn't
seem as far fetched and when you do get hit by it (as a 3rd party dev using
Wicket) it:
1) Is very hard to figure out what is going wrong.
2) Can't easily be fixed by yourself because the issue is basically in the
Wicket code.
I intend to try out the patch and report back my findings. With a bit of luck
the suggested patch can be easily merged into the next version of Wicket.
> Forms + ModalWindow + AjaxSubmitLink + FormComponent#isInputNullable
> --------------------------------------------------------------------
>
> Key: WICKET-1826
> URL: https://issues.apache.org/jira/browse/WICKET-1826
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.3.3
> Reporter: German Morales
> Priority: Minor
> Attachments: bug.zip, modalwindowform.jar, modalwindowform.jar,
> WICKET-1826.patch
>
>
> Submiting a form which is inside a ModalWindow, wicket javascript sends only
> the information for the modal window's form, but not for the root form of the
> page (because ModalWindow hangs its own div at body level).
> On Wicket server side, the form processing is done for the root form, which
> calls inputChanged for all the components in the page, but the javascript
> side didn't send the information for them, and then some of them go wrong.
> That happens to FormComponents which have isInputNullable in true.
> More description and proposed solutions in the (to be) attached quickstart
> project.
--
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
