[
https://issues.apache.org/jira/browse/WICKET-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1826.
---------------------------------
Resolution: Invalid
This shouldn't happen if you have form in your modal window. If that's the case
only the form inside modal window should be processed. Also in 1.3 if you have
modal window with panel with form, you should always place the modal window
inside another form.
If this problem still persists (in current 1.3 branch) please reopen the issue
> 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
> Assignee: Matej Knopp
> Priority: Minor
> Attachments: modalwindowform.jar
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
