It appears that bad things happen if you put a persistent object in session (not nhibernate session) and then try to access it later. I get "Could not initialize proxy - no Session." Before I start trying to dig into this too much I wanted to make sure it was or wasn't the way it should work. Thanks.

If you try to initialize any proxies and the session they were loaded in was closed, this is the error you get. Open a new session and reassociate the objects with it.

Can you post a code snippet demostrating that?

Maybe a link to an example?

if I was needed to reattach an object to a session, most of the time I am using session.Lock(myObject, LockMode.None); with this method, the object is completely reattached to the session but tells NH not to reload any data. Since you are expecting that the data of an object may have changed, you will probably have to do a session.Lock(myObject, LockMode.Upgrade) or LockMode.Read. you are right that session.Update() will work too, but i'm not entirely sure how you might be using the feature and they are not the same.

session.Update() sends an UPDATE to the database. this assumes you have updated the object yourself outside of a session and you want to be sure those changes are persisted when reattaching to a new session.

session.Lock() can be configured to attach a detached object back to a new session and check the database (using the <version> property) to see if any updates to the object have happened while it has been detached.

my previous post wasn't meant to offend anyone; i run into the occasional bug or missing feature, but by-and-large i feel this library is the best thing .NET has going for it.

I have a page in asp.net for testing purposes. I have one button that fires an event to load an appuser object from nhibernate and store it in the asp.net session. That's in one httprequest. Then I click another button that sets the value of a text box equal to the fax number of that appuser object.

The problem is that it will throw a lazyinitialization exception when reading the fax number. Why would I even get an nhibernate exception when I'm only trying to read a non lazily loaded property of an object I just stored in session?