make sure your callback sets the Wicket-Ajax header so wicket knows its an ajax request, otherwise it thinks you pressed refresh in the browser.
-igor On Fri, Jun 17, 2011 at 4:35 PM, bglynn <[email protected]> wrote: > I have a use case that requires a non-wicket client side ajax invoked on my > page. The client side request comes after a form submit has been made on the > model. For the client side ajax, I'm using a AbstractDefaultAjaxBehavior and > using it's getCallbackUrl to preform a wicketAjaxGet with additional > parameters to update my page model. Functionally, this is working, but the > page state is reset to the default model when the client side ajax is > invoked, as if its a new page request. What is required in order for the > non-wicket invoke to be aware of the latest page version? > > Thanks in advance! > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/callback-versioning-issue-tp3606799p3606799.html > Sent from the Users forum 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]
