Thanks a lot.
fljmayer wrote:
1. How do I control how much of my object graph gets serialized across relationships? I assume that I have to explicitely load lazily loaded collections, but that everything else will be serialized automatically. Is this correct?
emmanuel wrote:
Every non proxied, non lazy loaded collection will be in the object graph.
And what does that mean for lazy loaded collections? Will they be in the object graph if I initialize them somehow? And will they survive being attached to a new session?
fljmayer wrote:
2. Upon association with a new session, can Hibernate really figure out even complex object graphs if I set cascade="all"? The reason I ask is that I found this somewhat tricky in my value object implementation.
emmanuel wrote:
Would say yes, any specific pb
Difficulties only in my current approach with XDoclet-generated value objects, so I want to avoid further difficulties. Just found out the use of detached objects yesterday but the documentation is a bit spotty.
fljmayer wrote:
3. Are detached objects meant by something called 'long-running transactions' in the manual? I couldn't find a definition for this term anywhere in the manual.
emmanuel wrote:
It's a tx based on several user actions and usually based on several DB tx.
eg: finding a user by criteria and adding a new address is a user tx and a (not so) long-running one
So instead of using multiple sessions and detached objects I could also commit multiple times on the same session?