[
https://issues.apache.org/jira/browse/WICKET-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
German Morales reopened WICKET-1826:
------------------------------------
>This shouldn't happen if you have form in your modal window.
I have a form in my modal window, please check the source code.
Additionally, i'm attaching soon an extended quickstart project that shows how
a value entered in the modal window is displayed later in the page (to show
that the modal window form is working).
>If that's the case only the form inside modal window should be processed.
Well, that's not what seems to be happening, and that's the reason i posted
this issue in the first place.
>Also in 1.3 if you have modal window with panel with form, you should always
>place the modal window inside another form.
This phrase is not so clear to me.
Anyway, i've extended the demo project to include different versions:
-a modal window inside the page main form
-another modal window, inside a nested form (inside the page root form)
-another modal window, inside an additional form (outside the page root form)
Also, i'm providing 2 checkboxes this time:
-one inside the page main form
-an additional inside a nested form (inside the page root form)
In all cases, after closing any of the modal windows, the checkboxes values are
lost.
Perhaps you can clarify more what's wrong in the demo project?
Thanks in advance,
German
> 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.
