I have a graph with many levels of parent-children. I modeled this graph with lazy initialization. I need to load the top part of this graph in one session, modify it when necessary, and if needed load other sets of children in new subsequent sessions. At the end I cascade-update the whole graph.

Hibernate documentation specifies:
"The lock() method allows the application to reassociate an unmodified object with a new session." section 8.6.

Gavin said:
"For unmodified objects: session.lock(o, LockMode.NONE)
For modified objects: session.update(o)" in this thread:
http://forum.hibernate.org/viewtopic.php?t=926239&highlight=

I don't want to persist the changes to the loaded part until I am done (not just to lazy initialize a collection).
I was able to load children of a modified parent, without losing the changes to the parent with the following code:

session.lock(parent, LockMode.NONE);
if(!Hibernate.isInitialized(parent.getChildren())){
Hibernate.initialize(parent.getChildren());
}

What am I missing?

mota

Ahem, what is your problem? What exactly is not working?

I am locking (associating with a new session) a modified persistent object, and it is working. This is not supposed to work. Am I missing something?

Why should this not work. I think this is supported for a short time though, since 2.1 ? dont know exactly

Gavin said on December 10, 2003:
"For unmodified objects: session.lock(o, LockMode.NONE)
For modified objects: session.update(o)" in this thread:
http://forum.hibernate.org/viewtopic.ph ... highlight=

And I am using a Hibernate jar downloaded on November 29.

Gavin said it works, it does work for you, I dont get where your problem is.

Gavin said, for modified objects, we should use session.update() and not session.lock(). I am using *session.lock() for modified objects*

That just means your modifications will not be stored. You need to use session.update() for that.

If I can ask the question in different wording:
What does "session2.lock(o, LockMode.NONE)" do, when object o is loaded by session1 and modified after session1 is closed? session2 being the new session.

Is this supposed to just reassociate the modified object (as is) with the new session?

Exactly

That makes sense.

Thank you.