The issue is not urgent, I just want to metion it affects the architecture of applications using NHibernate.
I think it is an issue in the alpha state, and beta state is for minor changes and bug fixes. On Sat, Apr 18, 2009 at 1:05 PM, Yaojian <[email protected]> wrote: > BTW, I wonder if the ConnectionManager.Disconnect can bypass checking > IsInActiveTransaction if the session is opened by a supplied connection with > ISessionFactory.OpenSession(IDbConnection) > > > > > On Sat, Apr 18, 2009 at 12:53 PM, Yaojian <[email protected]> wrote: > >> All my exsiting code rely on TransactionScope .... the code runs well with >> NHibernate 2.01 GA. >> I migrate to NHibernate 2.1 as I generate NHibernate mappings on-the-fly, >> one System.Type is mapped to different entities through different >> "entity-name" rather than RuntimeType, of which 2.0.1 dose not support. >> >> If ISession represents a UnitOfWork, enabling the TransactionScope span >> multiple sessions will make the "UnitOfWork" compositable. The higher layer >> in the application will have a chance to composite multiple "UnitOfWork"s in >> the lower layer to a composited "UnitOfWork". >> >> Without TransactionScope support, NHibernate specific code will escape >> from the data access layer to business layer. >> >> >> On Sat, Apr 18, 2009 at 12:43 PM, Fabio Maulo <[email protected]>wrote: >> >>> 2009/4/18 Yaojian <[email protected]> >>> >>>> The session still can not be closed inside a TransactionScope, I think >>>> it is a major issue :-( >>>> >>>> http://nhjira.koah.net/browse/NH-1744 >>> >>> >>> Is it URGENT ? >>> >>> -- >>> Fabio Maulo >>> >> >> >
