Exception Handling
Workflow control brackets the transaction, so it must say what to do if the transaction aborts
An exception handler must know what state information is available
- cause of the abort, e.g., a status variable
- possibly program exception separate from abort reason
- for system failures, application must save state in stable storage; note that none of the aborted txn’s state will be available
Chained model - exception handler starts a new txn
COM+ - component returns a failure hresult