Bas,
This is what I wanted to find out if you guys use a different model for
new items(before saving them).
I had previously headed in the wrong way by not using LDM so I wanted to
be sure I'm doing it correctly now.
Thanks,
Alexandru
On 03/04/2011 04:19 PM, Bas Gooren wrote:
Hi,
I use a custom refreshingview which uses a LDM for existing items, and
a serializing model for new items. When converting the input in my
custom refreshingview (which is the component that "owns" the list) I
handle both types of models. On refresh (re-display) it "replaces" the
serializing models with LDMs if they are saved.
Hope this helps :-)
Bas
Op 4-3-2011 15:14, Alexandru Artimon schreef:
Not really,
I want to find out what you guys do when in a form you add a new item
to a collection(where the items are passed to a LDM and then showed).
Do you save first the item and then pass it to a LDM? Or do you use a
plain model? Or maybe something else?
I'm trying to see that I'm not headed on the wrong track.
Thanks,
Alexandru
On 03/04/2011 03:57 PM, mzem...@osc.state.ny.us wrote:
Not completely sure what you're getting at, would RefreshingView
help you?
http://wicket.apache.org/apidocs/1.4/org/apache/wicket/markup/repeater/RefreshingView.html
From: Alexandru Artimon<aarti...@dgfoundation.org>
To: users@wicket.apache.org
Date: 03/04/2011 08:31 AM
Subject: LoadableDetachableModel small issue
Hi guys,
Thanks again for the previous help with the LoadableDetachableModel.
Now I have a "workflow problem" related to LDM for which I think you
guys might have a more elegant solution.
I have a hibernate collection which is shown by a ListView. Each
item is
passed to a LDM and rendered with a custom component. Now the
problem is
when the user wants to add new items to the collection. Due to the use
of the LDM I need to first save the empty-item in the DB just to
receive
an id which the LDM can use later to load the object. Acceptable, but
what if the user decides to leave the page without saving the form. At
the next load the empty-items will be there which is not the desired
functionality.
How do you guys handle new items which need to be passed to a LDM (in
order to avoid all those problems generated by the Wicket Serializable
Checker) ?
Thanks a lot,
Alexandru
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Notice: This communication, including any attachments, is intended
solely
for the use of the individual or entity to which it is addressed. This
communication may contain information that is protected from disclosure
under State and/or Federal law. Please notify the sender immediately if
you have received this communication in error and delete this email
from
your system. If you are not the intended recipient, you are
requested not
to disclose, copy, distribute or take any action in reliance on the
contents of this information.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
