> And especially with Hibernate I do *not* want my models detached because I > consider a DB lookup to be > expensive and any writable entity is versioned. The session is never kept in > my models because I use EJBs > for DB access, so I keep only EJB stubs in my model objects and those are > fine to serialize. Every component and model is detached before serialization (at the end of each request). The detach method can wipe out non serializable dependencies, remove stuff that can be easily recreated, etc. Lookup of entities is definitely not slow, especially not with second level cache.
-Matej > > Do you have any documentation links or classes to start looking for what's > happing when a component > tree is re-attached and/or de-serialized (if this is the same with wicket)? > >
