you are using ajaxformcomponentupdatingbehavior which is made specifically for updating components. nothing is stopping you from using ajaxeventbehavior to bypass default form processing and do whatever you want however you want.
what we offer here are the defaults, they do not use any special api that you do not have access to. if the default doesnt work how you want then roll your own. you might think that the default is backwards, but consider this: you are the first person to think its backwards in well over a couple of years that wicket had ajax support. -igor On Mon, Oct 27, 2008 at 4:14 PM, Dreamage <[EMAIL PROTECTED]> wrote: > > Anyway the point is that when using ajax components, the associated model is > updated but the form may not be submitted yet, so how would you implement a > cancel button to undo the ajax model updates ? Do we have to do all this by > hand (storing ajax model updates in temporary variables and applying the > values to the real models in the onSubmit method of the form) or is there > another way ? > > -- > View this message in context: > http://www.nabble.com/Ajax-form-components-principles-tp20180246p20198434.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
