I know there is some sourcecode for Wicket that can reattach objects automatically, but you need to put the entity in some sort of container (model) that can deal with the reattaching part. But I`m not too happy with this solution because it makes pages less clear. I never did this when I used
Peter Veentjer - Anchor Men wrote:
What didn't you use in swing? No models? that is not really possible you
have to use models in swing (and also in wicket)
I don`t think you understand my reply. I have no problems with models, but I have problems with wrappers around objects
Matej Knopp wrote:
How can you ensure that a session will be closed? What if user got
disconnected? Will the session hang open until the http session timeout?
Another problem that comes to my mind is that hibernate session is not
thread safe. Using one session through multiple request you
I still don't understand what you find so complex around a simple model
that handles the detach/attach for youre components.
---
To be honest I don`t think wrapping a single object can be called a model, it
is just a wrapper. And I don`t have much problems with it
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
