I am glad you got that right :)
If the model has changed, call modelChanged() on the form (and/or the
form components, not sure). There is no need to again set the model.
Regards,
Erik.
Troy Cauble wrote:
in a form that gets reused (repetitively in the same page).
Don't you ever re-use a component! Sharing models/behaviors is fine, sharing
components is not.
Thanks, Erik, but I'm pretty sure we're talking about different things.
I'm just using components on a page and changing the data.
(Reusing the form *over time*.)
I have
Page
DropDownChoice
Form
Fields
When an entity is selected with the DDC, the
form is made visible and filled with the model/data
of the entity. When a save button is hit the form
is hidden and the DDC reset ("Choose one...").
You're not saying the Form should be discarded and rebuilt,
are you?
Thanks,
-troy
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
