Transaction Services
Castle.Service.Transaction was inspired by the Java Transaction API (JTA), although it is a simplified version with no support for two phase commit.
Basically there is a transaction manager that is able to create transactions, that are associated with the thread. You can only have one active transaction per thread.
The transaction object only orchestrates the resources enlisted with it. It is up to the resource implementation to provide integration with some external transaction-capable entity, typically a database connection.
Attributes | Interfaces | Classes |
Found an error? Something inaccurate?
Help us improve the documentation
Generated by Castle Anakia.
Generated by Castle Anakia.
Sponsored by 
Castle Stronghold.