n Behalf Of Igor Vaynberg
Sent: 17. juli 2006 17:32
To:
wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Playing
with models:)/wicket.extensions.markup.html.form.palette.Palette;
components whose model is
backed by a collection do not always call setobject() because they work on the
col
Vaynberg
Sent: 17. juli 2006 17:32
To:
wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Playing
with models:)/wicket.extensions.markup.html.form.palette.Palette;
components whose model is
backed by a collection do not always call setobject() because they work on the
collection
Of Eelco HilleniusSent: 17. juli 2006 12:14To:
wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] Playing with models:) /wicket.extensions.markup.html.form.palette.Palette;>> When is setObject supposed to get called, Cause I only see it get called during
> construct?Whenever a (for
: Re: [Wicket-user] Playing with models:)
/wicket.extensions.markup.html.form.palette.Palette;
>
> When is setObject supposed to get called, Cause I only see it get called
> during
> construct?
Whenever a (form)component has to update it's model contents. Or if
you call setObj
>
> When is setObject supposed to get called, Cause I only see it get called
> during
> construct?
Whenever a (form)component has to update it's model contents. Or if
you call setObject explicitly of course :() Typically, a component
update is done by Form, which visits all it's children and cal
