Hello all... I´m wondering how can I handle exceptions using "NHibernate Best Practices" : http://www.codeproject.com/aspnet/NHibe ... ctices.asp

I mean, the commit occurs only in the end of http request, so I have no control on it....

Help?

ty

Not a direct answer to your question, but you may want to consider implementing the Unit of Work pattern and changing your FlushMode to Commit Only... This avoid transparent write behind but I prefer it for giving me greater control over when things happen with persistence.
If you look at Billy's code, he catches exceptions to rollback the transaction at least.
I wrap Hibernate exceptions for handling higher up in the layers.

Not sure this helps but maybe another idea.