"other stuff" are for example the Cache. Oren has improved the transaction management, inside DTC, a lot trying to avoid the explicit usage of NH's transaction. Perhaps the "implicit NH's transaction" could be the final-cut
On Fri, Mar 4, 2011 at 3:50 PM, Jeff Sternal <[email protected]> wrote: > I've seen that issue, but based on what I've seen running our own > integration tests, that behavior could break in some of the scenarios we > run, particularly inside nested transaction scopes. > > What is the 'other stuff' you mention? I've seen you go back and forth with > Ayende on this issue before, but never seen a clear list of reasons why we > should use both TransactionScope and NH transactions. > > The issue I'm raising seems to be a candidate - but if you could weigh in > on the intended behavior, I think the fix I suggested above would solve it > (though I'm still getting ready to run tests on the trunk to make sure). > -- Fabio Maulo
