Yupeee... can't wait! Thanks 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 at http://groups.google.com/group/castle-project-users?hl=en.
