I read it a couple of places but have not done my own testing (yet) -- this is a link to a fairly long blog entry about the problem. The author of the blog posts a comment (right at the bottom, third-last comment) to the effect that it is not a problem in NH3.1.
http://davybrion.com/blog/2010/05/avoiding-leaking-connections-with-nhiberna te-and-transactionscope/ Cheers -- John -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Henry Conceição Sent: Thursday, 5 January 2012 3:38 PM To: [email protected] Subject: Re: Castle.Facilities.NHibernateIntegration It's? Where did you saw it? Cheers, Henry Conceição On Thu, Jan 5, 2012 at 3:13 AM, John Jeffery <[email protected]> wrote: > I was under the impression that the need to declare a session > transaction inside a transaction scope was fixed with NH 3.0 and > later? Do you think it is still necessary? > > I for one would be very interested to see what you are doing with NH > integration with Castle Henry, if you ever get it to the point where > you want to show someone else. > > Cheers -- John > > On Jan 5, 1:54 pm, Henry Conceição <[email protected]> wrote: >> A simple update of tx the machinery doesn't work. At least if you >> want to follow the guidelines preached by nhibernate (even with a >> ambient tx, you must have begin session transaction). The simplest >> way it to go with implicit session transaction (like henrik's >> facility does), but it can lead to nasty dtc issues (from what i've >> read on blogs and stackoverflow). >> >> I'm trying to get they working together, but I'm not confident in >> publish it atm. Want to test it a little more.... >> >> Cheers, >> Henry Conceição >> >> >> >> >> >> >> >> On Thu, Jan 5, 2012 at 1:21 AM, ross <[email protected]> wrote: >> > Hi John, >> >> > I'm using an older version - 2.5.1.0- which still works ok. >> >> > The reason for this is because it compiles in .Net 3.5 which is a >> > requirement for the project I'm working on. >> >> > The 3.x version uses some .Net 4.0 specific features- I did manage >> > to replace most of them at one stage but due to time constraints >> > didn't get back around to it. >> >> > Cheers, >> >> > Ross. >> >> > On Jan 5, 1:10 pm, John Jeffery <[email protected]> wrote: >> >> Hi Ross, >> >> >> What version of Castle.Services.Transactions were you using? I am >> >> interested in getting the NH facility going as well, and I checked >> >> out from the trunk and applied your patch. >> >> >> All good so far, but I am also getting a compile error in src >> >> \Castle.Facilities.NHibernateIntegration\Internal\ResourceAdapter. >> >> cs >> >> >> The ResourceAdapter class implements an interface >> >> Castle.Services.Transactions.IResource, which no longer exists in >> >> the latest version of Castle.Services.Transactions (I used version >> >> 3.0.202.2202 from nuget). I have had a look around trying to work >> >> out if this interface has been renamed or moved, but it would >> >> appear that it has been completely removed. Any suggestions gratefully received. >> >> >> Cheers -- John >> >> >> On Dec 21 2011, 11:19 am, ross <[email protected]> wrote: >> >> >> > Posted the issue and some patches to the issue tracker: >> >> >> >http://issues.castleproject.org/issue/FACILITIES-156 >> >> >> > On Dec 19, 4:40 pm, ross <[email protected]> wrote:> Hi >> >> > All, >> >> >> > > I posted on Stack Overflow previously as I was having trouble >> >> > > with the NHibernateIntegration facility in Windsor when >> >> > > working alongside Castle Windsor 3. The question is located at: >> >> >> > >http://stackoverflow.com/questions/8557327/castle-windsor-3-fluent-nh... >> >> >> > > I have since recompiled the NHibernateIntegration Facility DLL >> >> > > file with a few changes to get it working and was wondering if >> >> > > this is worth creating a patch for? The changes are: >> >> >> > > For src\Castle.Facilities.NHibernateIntegration\Internal >> >> > > \SessionFactoryActivator.cs: >> >> >> > > Before: public override object Create(CreationContext context) >> >> > > After: public override object Create(CreationContext context, >> >> > > Burden >> >> > > burden) >> >> >> > > For src\Castle.Facilities.NHibernateIntegration\Internal >> >> > > \NHSessionComponentInspector.cs >> >> >> > > Before: model.Dependencies.Add(new >> >> > > DependencyModel(DependencyType.Service, null, >> >> > > typeof(NHSessionInterceptor), false)); >> >> >> > > After: model.Dependencies.Add(new DependencyModel(null, >> >> > > typeof(NHSessionInterceptor), false)); >> >> >> > > Thanks, >> >> >> > > Ross.- Hide quoted text - >> >> >> - Show quoted text - >> >> > -- >> > You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to [email protected]. >> > For more options, visit this group athttp://groups.google.com/group/castle-project-devel?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
