What are you willing to call for a component constructor?
like textfield: And you don't have to worry about the underlying detachable
code.. That
just happens.
------------------------------------
If you use the objects in a view this wouldn`t be much of a problem. But
sometimes a Page needs objects that aren`t viewed, but are required in a
'service' for example. Try to explain why that object now must be wrapped in a
model.. altough you never use it as a model. You only use one feature of the
model: dealing with detached objects.
But how is that services object loaded?
If you do that youreself in a session then you can detach it yourself
(on the same place a Hibernate Session is detached. See youre onw
RequestCycle implementation)
Then other developers that are using that code/services don't have to
think about closing the service. Just as they don't need to bother about
closing the hibernate session
(and all others kinds of objects that are connected to a component
through a detachable model)
So please give me a concrete example how it is done now in detachable model.
And then an example you you would do it.
Also models are not really just wrappers around objects that are always
exactly get with getModelObject(). They can be property bases so that
you get a piece of that object.
And in that same light you could also say that a DocumentModel of swing
is also just a wrapper (around text)
johan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
