Is it expected that I must reattach (lock) in this case an entity if the previous session was closed from the first request and I am on a subsequent request that uses the One Session per Request pattern?

The problem Im having is I have an entity (A) that contains a set of entities (B) during a subsequent postback I want to actually load the content (lazily) of the set which itself points to an entity (C) which isn't yet loaded.

It appears that if I do not reattach the entity (C) I get a LazyInitializationException that there is No Session. It appears that even though I have a session the Javassist handler proxy doesn't automatically look it up.

What do you do in this situation? I could reload the A entity and rewalk the tree but the list of Entities B is always a different order which causes confusion for JSF.

I think you can use the Hibernate.initialize(yourObject.lazyObjectAccessor()) method to have Hibernate flesh out the proxy objects.

You may need to use a session.merge() method first, but I'm not 100% on that part.

I would certainly give it a try.

Hibernate.initialize(object) works if I put it in the exact same location as Session.lock(object,NOLOCK) It doesn't seem to work if I try this on the collection SET or if I do it to its parent.

I was thinking it might be a cascade issue so I set it to cascade="all" but that didn't change anything.

Maybe I am expecting too much from Hibernate. I think it would be nice to be able to reattach the parent object to the session that it should then use this session on all of its children.

OK I apparently missed something whiule reading JPWH. It appears that my issue is associated with the fact that cacscade was not set properly. In this case I set it to all (other options may work)

Setting the parent to Hibernate.initialize(object) made no discernable change to the children's children. However, Hibernate.initialize(object) does work if you do this for the lazy object itself. This requires the methods in the POJO to know about Hibernate, which for me is not desireable.

Setting the parent to getSessionFactory().getCurrentSession().lock(object,LockMode.NONE); Did affect the children such that while they were in a lazy detached state originally, they were reattached to the session and no "No Session" exception was thrown. The parent object in this case is not a proxy as far as I can tell from the variable inspection.

Lesson learned watch the cascade option on many-to-one