Hi,
i never had the need to have 2 special models for new and existing
objects
What is then the difference?
The only thing a model really does it getting the modelObject. So
what you put in that can be an existing one or just a new Room()
Please give a better usecase for this
but "getting the modelObject" could differ. An existing object can be
detached, so a LoadableDetachableModel could be used, while a new
object may not be detached and needs to be stored in the session. I
know this could be done with a DetachableModel itself and so it's a
bad usecase.
I'm just wondering why there is no way bind child objects and their
properties in exactly the same way in which normal properties are
bound - automatically using the id of a container in between... But
for me it's ok to use the PropertyModel as well, I just thought I
should avoid this as replacing the model is allowed...
Regards,
Ralf
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
