I'm in the process of migrating to 3.2.x and have encountered a strange LIE when walking the object graph.

I re-attach object A.
openSession.lock(a, LockMode.NONE);

I iterate through A's children of type B.

from there, I walk a chain of 3 many-to-one relationships: C, D, E.
(Note: all have no lazy attribute defined.)

Any invokation on E, will throw the LIE.

C & D's proxies seem to be fine, but E is hosed. This same code has been working for years on Hibernate 2.x and I did not find any migration note that would suggest that I cannot walk my hibernate graph as I used to.

Any help is much appreciated.

I was able to determine that sometimes part of this graph had been loaded in a previous session and was still detached.

Not sure why this works in Hibernate 2.x, but checking to see if each entity is currently attached to the session, and then re-attaching it using
the session.lock(entity, LockMode.NONE) seemed to do the trick.