[
https://issues.apache.org/jira/browse/WICKET-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855307#action_12855307
]
Padmaja Kota commented on WICKET-1826:
--------------------------------------
I can still the same issue occuring with Wicket 1.3.5 .
My modal window is like :
<panel>
<form>
remaining form components..
</form>
</panel>
However each time i submit the form the parent form which contains this modal
window is also submitted and the inputs on the parent form are set to null
causing error in my use case.
> 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, 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.
