The problem is that usually the DTC is opened by a lower level component, and my code has no control over it.More than that, I usually don't have control over NH's code as well.
It goes like this: 1/ low level infrastructure - dtc 2/ high level infarstruture - nh 3/ business code - my stuff I don't want to be aware of all of this issues, I just want to make this work. So explicitly flushing is an option that I would generally be against. Making NH's transaction equal to the dtc is also not a good option, because the use of the DTC is to manage several resources, not just NH. On Mon, Mar 23, 2009 at 11:15 AM, Fabio Maulo <[email protected]> wrote: > 2009/3/23 Ayende Rahien <[email protected]> > >> We can make this work, but this doesn't look like a good idea to me.Now >> we essentially have to commit the tx twice. >> We might as well just call Flush here, since that is what it would >> translate to. >> > > In a WEB where is the session Open and where is the DTC ? > Who encapsulate what ? > In which tier is the DTC and in which is nhSession+nhTransaction ? > The nhTransaction should work as a DTC instead a ADO.NET-transaction in > certain cases ? > Is, the nhTransaction, an abstraction of Transaction ? (ADO.NET or DTC) > > And the last question: > How big is the universe ? ;) hahahaha > -- > Fabio Maulo >
