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 at http://groups.google.com/group/castle-project-users?hl=en.
