default processing = false means do not validate, etc. but, inputs are preserved. make sure your ajaxsubmitlink is inside the correct form. you can specify one in its constructor.
-igor On Thu, Jun 2, 2011 at 4:22 PM, Nelson Segura <nsegu...@gmail.com> wrote: > On the AjaxSubmitLink, correct? > When I do that, the input of the other fields is lost (which has not been > previously submitted). > How does wicket exactly decides whether to show the model value or the user > raw input? > My Ajax links is refreshing the whole panel. > -Nelson > > > On Thu, Jun 2, 2011 at 4:14 PM, Igor Vaynberg <igor.vaynb...@gmail.com>wrote: > >> you want setDefaultFormProcessing(false) >> >> -igor >> >> On Thu, Jun 2, 2011 at 3:41 PM, Nelson Segura <nsegu...@gmail.com> wrote: >> > I have a form to which I need to add dynamic fields using ajax, whenever >> the >> > user clicks on the "add new input" link. >> > I need to preserve the current user input, without actually updating the >> > backing models (or at least preserve input that is not completely valid, >> or >> > do not show errors if the user as not entered a required field) >> > >> > I am using an AjaxSubmitLink to submit the current user input, but >> > >> > (a) I am not able to preserve the input (if I use >> > setDefaultFormProcessing(true)) >> > (b) I get validation errors, or lose invalid input if I try to mock with >> the >> > onError() method of the AjaxSubmitLink >> > >> > What is the correct way to do this? >> > >> > -Nelson >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
