You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by puschteblume <pu...@gmx.de> on 2008/08/15 21:27:21 UTC

don't understand model behaviour for a form and a datatable

I have a DataTable in a Panel which creates a Subpanel by an AjaxRequest 
with a form in it. The form shows the double-clicked entry of a 
DataTable's row, where the objects parameters can be changed by pressing 
the save button. The form is constructed by a CompoundPropertyModel.

And now comes the magic I don't understand: If I press the "save" button 
the object in the table will immediately updated although the submit 
methods are empty.

How does this behavior work? How can I interupt this update if I have a 
problem on the backend?

Heiko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: don't understand model behaviour for a form and a datatable

Posted by Johan Compagner <jc...@gmail.com>.
What do you mean submit methods are empty? You form or button submit?
It doesnt matter if there is an impl or not, when those methods are
called the model(s) have there new value so that you can do save() of
that object in the submit method.

If submit isnt called then conversion or validation has failed.

If you detect an error in the submit then you just have to report that
to the user and 'throw away' that object (detach)

Johan

On 8/15/08, puschteblume <pu...@gmx.de> wrote:
> I have a DataTable in a Panel which creates a Subpanel by an AjaxRequest
> with a form in it. The form shows the double-clicked entry of a
> DataTable's row, where the objects parameters can be changed by pressing
> the save button. The form is constructed by a CompoundPropertyModel.
>
> And now comes the magic I don't understand: If I press the "save" button
> the object in the table will immediately updated although the submit
> methods are empty.
>
> How does this behavior work? How can I interupt this update if I have a
> problem on the backend?
>
> Heiko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org