On Tue, Jul 20, 2010 at 12:53 AM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
> Typically, I use LDM's for every place that I am viewing data, and a regular
> serializable model for places that I'm editing data.  You must be able to
> persist changes across requests (without persisting to the long-term
> storage), which means that you'll need to be able to serialize things.

this is not true :) the formcomponents themselves preserve the state
so using an LDM for a form is feasible. the sequence is basically

* load entity - model
* call setters - form component models
* flush/close session - somewhere


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

Reply via email to