://www.nabble.com/Session-Objects-Approach-tf4600804.html#a13229389
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Just trying to be helpful. :-)
Igor Vaynberg wrote:
I think what you all are missing in this discussion is that ldms are
mostly uss for read only data, not for forms.
-igor
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
I found another con with detachable is that if you are constructing a complex
object graph _before_ putting it in the database you would have to do
something cleverer... e.g. only detach if already persisted? We just stuck
with non-detachable models.
But the solution to that might be easy:
Does this approach have any significant improvement over the former? and
what could be the cons
Like Alex said, look at LoadableDetachableModel for instance. You
don't have to discard right away; just do at at the end of the
request. It's what detachable is for.
Pro detaching: less memory
Basically there is an object like this, a common model
class User{
Long id;
String username;
String password;
String fullname;
...
List collections;
}
From most examples and basic approach, i see references to this Object in
the session
During user sign in, this object is loaded from
:
http://www.nabble.com/Session-Objects-Approach-tf4600804.html#a13143236
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
