Hi all!
I need to persist a deeply nested object graph (5-6 levels). Objects in some levels could have been already persisted while others are new to the session. With hibernate 2.x I did a saveOrUpdateCopy() of the graph. According to the
migration guide I should do a merge() with hibernate 3.x. But the fact is that for cases as A--*B--*C (say, A is the parent of Bs which in turn are the parents of Cs, the relationships are all bidirectional associations and cascades=all...as in chaper 22) won't work. Because if B and C are new to the session, as B in not attached to it by merge(), hibernate will complaint that the (to-parent) reference from C to B is one to a non-persisted object.
How can I get the old saveOrUpdateCopy() behaviour back?
Thank you in advance.
Regards,
Carlos

I would think that "saveOrUpdate" should work fine... Are these detached objects or are have all been loaded in the same session?

For some of them there are previous persistant instances attached with the session so saveOrUpdate() will fail. Other are completely new to the session (the instances were created but never persisted yet). So cascading merge() will fail for other objects which refer to these (for example their children in a bidirectional parent-child relationship). So I see no way to take the root of the graph and persist the entire graph via cascading. I did this with saveOrUpdateCopy() in hibernate 2.x. But even the behaviour of saveOrUpdateCopy() in the 2.x-compatibility Session interface provided by hibernate 3.x differs from that of the original 2.x Session (it fails in the same way that merge() does). So for now I'm downgrading to 2.x and it works fine. But eventually I would like to migrate to 3.x.
Regards,
Carlos