I have track this down to the Component#modelChanging() method, it seems
that the actual modified page is not being stored in the session
(perhaps it has something to do with dirty pages?). I'm a bit lost here,
any clue would be appreciated.
Thank you.
On 29/08/13 14:33, Edgar Merino wrote:
Hello, I'm having a problem with a FormComponent I'm implementing, I'm
manually calling FormComponent#validate(), FormComponent#valid() and
FormComponent#updateModel() inside MyBehavior#onRequest() since the
object is not attached to a Form, I'm using a custom Behavior
(MyBehavior, which extends AbstractAjaxBehavior, I don't need any of
the functionality provided by AjaxDefaultAbstractBehavior), the model
changes for this request but every time a new request is handled I see
the component still uses the old model that was supposed to be
replaced in the previous request.
By debugging the application I can see that everytime a new request is
handled, the FormComponent will look for the model in the
Component#data attribute array, which holds the initially set IModel
and is never changed... I don't have a clue on how to change this, I
bet this is the key to solve this, does anyone have a clue on how to
do this?
Thanks in advance,
Edgar Merino.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org