I don't remember encountering problems with any of them. I compiled Castle.Services.Transaction, Castle.Facilities.AutomaticTransactionManagement and Castle.Facilities.ActiveRecordIntegration (I think on this last one I encountered an insignificant change in a method definition) against the latest version of core.
Btw, it would be nice, with this release, to update the various integrations as well. Effectively they are the ones that bring real value to cross-resource transactions, and being so small, it would be a shame to leave them behind. Well, I'm talking from the perspective of 1.x version of transactions. Can't say anything about the 2.x version though as I didn't have a chance to see it. On Mar 1, 12:20 am, "Henrik Feldt" <[email protected]> wrote: > Hi, > > Well, I'm technically not asleep yet and I haven't discussed time-zones. ;) > > I'm currently updatinghttp://github.com/hafwith the latest code, but > there's a bit of trickery with the submodules... > > Tell me; are all the dependencies you are using coherent with each other? > I'm going to depend on the latest versions of all of them... > > Regards, > Henrik > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of MoonStorm > Sent: den 1 mars 2010 00:49 > To: Castle Project Users > Subject: Re: Transaction Management - The chain of resources not rolled back > if one fails > > No release today... :( > > Btw, could you tell me where the latest code is located? I had a look > at the SVN repository and the build server output and it's all old. > Could you point me to the right location please? > > On Feb 27, 7:40 pm, "Henrik Feldt" <[email protected]> wrote: > > Roger that, I've had the same problem. > > > Fix coming up tomorrow together with release. > > > Cheers, > > Henrik > > > -----Original Message----- > > From: [email protected] > > > [mailto:[email protected]] On Behalf Of MoonStorm > > Sent: den 27 februari 2010 19:06 > > To: Castle Project Users > > Subject: Transaction Management - The chain of resources not rolled back > if > > one fails > > > Here is a simple scenario using the existing implementation of > > Castle.Services.Transaction > > > Transaction manager receives a green light for resource chain commit > > and calls every resource enlisted. > > Resource1 tries to commit but fails with an exception. > > AbstractTransaction cathes the exception and stores it for later use; > > the transaction is also given an invalid state. > > Resource2 is called now (surprisingly for commit!). > > At the end of the chain, the aforementioned exception is wrapped and > > re-thrown. > > > With this in mind, having the AR facility in place and my custom > > resource registered as well, a DB commit may fail but my component > > will commit, leaving the system in an unstable state. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Castle Project Users" 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-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" 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-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en.
