Transaction Support in Service Instances
All Service instances are
instantiated and executed as part of a Transaction Scope in the
SmartObjectBroker. The transaction option as specified on the SmartObject
method determines the TransactionScopeOption.
We have three options:
- Continue: TransactionScopeOption = Suppressed - No transaction, all services (execution blocks) will execute even if one or more fail.
- Stop: TransactionScopeOption = Suppressed – No transaction, execution will halt immediately after first service execution fails.
- Rollback: TransactionScopeOption = Required – A root transaction is created and will be the relating transaction for all participating services to obtain in.
The concept of Transaction Scope and ambient
transactions is clearly explained in the following article
No comments:
Post a Comment