I have called Session.Delete(object) and it threw an exception(a valid exception due to some foriegn key constrained). I catched the exception and then did Session.Rollback(). Then the problem occurs that everytime i call the list of the above type objects in the same session it gives me the same exception(not able to delete object due to foreign key constraint).

Only solution that works is Session.Clear() which i dont want to call as i want to use some of the data which is maintained by Session.

Thanx in Anticipation
Saurabh

I believe that the recommended approach is that when a session throws an exception you should close the session and open a new one.

Cheers,

Symon.

But in that case we wont be able to use the lazy loading on the object previously made. Also when i query about other objects the session works fine except the object the type when the error is thrown.

Saurabh

@Saurabh -
I don't get your second comment, but you can reattach objects using session.Lock to reattach your previously created proxy objects to the new session after you rolled back the transaction.
MIKE

Is there a simple way to find ALL proxies, existed in session before exception?

Now we use a single permanent session in out app (WinForms) and we may have a bunch of proxies. We use static Repository class and underlying PersistentManager class (a kind of SessionFactory+Session wrapper) to encapsulate all NHibernate stuff, so it seems to be reasonable to add session recreation and proxies rebinding code to this layer - after each transaction rollback in catch blocks.

BTW maybe there is some opportunity to get rid of permanent session without loosing lazy load capabilities? Maybe a sort of proxy access interception or LazyInitializationException handling - to reattach proxy to session, perform it's initialization and then disconnect?
Please forgive if it is are a stupid question, I'm just a newbie to all this stuff...