...@clarksnutrition.com]
Sent: Friday, August 21, 2009 12:43 PM
To: users@wicket.apache.org
Subject: RE: LoadableDetachableModel#load() called twice
Ok, I see what is happening. I am using one of the selected choice
objects in the onSubmit and then adding a new choice object to the list.
In order
he.org
Subject: Re: LoadableDetachableModel#load() called twice
Warren,
Unless you are indirectly calling load() yourself, eg by calling
getObject(), on your LDM) during form processing it's Wicket converting
the selected item (by choice id) to the actual "choice" object, by
matching the id aga
Warren,
Unless you are indirectly calling load() yourself, eg by calling
getObject(), on your LDM) during form processing it's Wicket converting the
selected item (by choice id) to the actual "choice" object, by matching the
id against the list of choices, calling load() on your LDM in the proces
I have a ListChoice that I add a choice to. I do this in an
AjaxButton#onSubmit(...). The problem is that load() has been called
before onSubmit() and I have to call LoadableDetachableMode#detach()
and have load() called again. This seems like a waste to have load()
called twice in order to get the
