Thank you Erik,
You should use Buttons instead of links. Button (or AjaxFallbackButton)
does submit the form.
Why, should I submit using links? we've just done it using a nested
form and attaching a AjaxSubmitLink to it.
The only thing you need to do is disable
validation on the button
Hello Maurice,
We just (almost) implemented this component (as I wrote in response to
Erik's post), but we're are now struggling with not processing the
form and retaining user input
other than that I have the same wondering, if I submit only the inner
form, will the browser send the whole form,
Hi Wojciech,
I am sorry, it appeared I wrote too quickly. This morning I found out
that what I wrote mostly does not work.
You /can/ call processInput() on any form component (if not all). This
will make that particular form component puts its value in the model.
But any way, the nested forms
Hello
This time my question is not so general.
We have a big form, part of this form there is a component which
should be a dynamic list of fields like this:
|TextField| - remove
|TextField| - remove
|TextField| - remove
|TextField| - add
if you click add another row |TextField| - remove
We usually follow this approach
-load initial list
-clone initial list for working copy
-if the list is likely to be altered often or by multiple persons
store a flag for each item indicating if it was removed or added
-have wicket modify the working copy (and or the flags)
-in the onsubmit load a
Thank you for our opinion Maurice,
problem is that what you're telling me is not exactly my problem
(although it will be further on, so thank you anyway)
as I see I have to submit the whole form in order to retain (not yet
save do DB!) those values from this particular dynamic list component,
I
Hi Wojciech,
You should use Buttons instead of links. Button (or AjaxFallbackButton)
does submit the form. The only thing you need to do is disable
validation on the button (call button.setDefaultFormProcessing(false)),
otherwise the onSubmit of the button is not called when some field in
Actually AjaxFormComponentUpdatingBehavior accomplishes the desired
behavior without submitting the entire form. I can see the tricky part
in loosing changes to the text in the textfields if you replace the
div surrounding them but i thought nested forms in wicket 1.3.? solved
this by only
