Hi,

I am using the Session per HttpRequest pattern in my ASP.NET 2.0 project using NHibernate 1.01.

On one of my pages, I store a loaded object in HttpSession and when the page submits I reassociate it with the CurrentSession in Context by using ISession.Lock(o, LockMode.None) or ISession.Update(o). Then, when I try to access a collection of the object I get the lazy loading error.

If I touch the collection during the loading of the object. No such error pops up.

Do I have to touch all collections in the loading session to make them accessable in the reassoicated session?

Thanks

Hongze

Hi,

I finally resolve the problem. The class relationship is as following:

A references B with many-to-one relationship;
B references C with a set lazily loaded.

When I use None cascading mapping for A referencing B, the error pops up if I try to access a.B.Cs in a reassociated session for a. If save-update cascade value is used, the lazy access works fine.

Can anybody explain this for me?

Thanks,

Hongze

After fixing the problem in my project, I tried some tests. I found if there are any references(many-to-one) on the path to a lazily loaded set, the loading will fail in a ressociated session:

[/code]

This behavior occurs because when you call Lock on A, A.B does not get locked automatically (unless its cascade is set to save-update, as far as I remember). You have to call Lock on A.B for lazy loading of B.CSet to work.