for a new entity you can always return a new entity. There is no need
to keep the filled in data between requests :-) as the fields have the
data already... When you return a new object Wicket's form update
mechanism will repopulate the object's fields.
Martijn
On 4/19/08, Fernando Wermus [EMAIL
On Fri, Apr 18, 2008 at 11:50:59PM -0300, Fernando Wermus wrote:
I try to spend the less memory I can using LoadableDetachableModel. But if
the user is filling up a form for a new entity I think I have two options,
one serialize and the other create a kind of dto. I don't like the first
In this case, yeah I think the best way to go is with a DTO. You could use a
static Inner POJO class.
cheers
On Fri, Apr 18, 2008 at 5:50 PM, Fernando Wermus [EMAIL PROTECTED]
wrote:
I am finishing my first app for production in wicket. As any newbie I try
to
make a side relevant
I like for my entities to always be serializable. Is there some
special requirement to have a non-serializable field on your entity
class?
On Fri, Apr 18, 2008 at 4:50 PM, Fernando Wermus
[EMAIL PROTECTED] wrote:
I am finishing my first app for production in wicket. As any newbie I try to
I try to spend the less memory I can using LoadableDetachableModel. But if
the user is filling up a form for a new entity I think I have two options,
one serialize and the other create a kind of dto. I don't like the first
because I don't want my domain model be modified by the web tier
