FOR ADF Transaction:
No Controller Transaction: The called bounded task flow does not participate in any ADF Controller transaction management.
Always Begin New Transaction: A new transaction starts when the bounded task flow is entered, regardless of whether or not a transaction is in progress. The new transaction completes when the bounded task flow exits.
Always Use Existing Transaction: When called, the bounded task flow participates in an existing transaction already in progress.
Use Existing Transaction if Possible: When called, the bounded task flow either participates in an existing transaction if one exists, or starts a new transaction upon entry of the bounded task flow if one doesn't exist.
Commit and Rollback must be specified for 'Always Begin New Transaction' and 'Use Existing Transaction if Possible'.
There are four transaction options that a bounded task flow can use (note that unbounded task flow doesn't support transaction):
No Controller Transaction: The called bounded task flow does not participate in any ADF Controller transaction management.
Always Begin New Transaction: A new transaction starts when the bounded task flow is entered, regardless of whether or not a transaction is in progress. The new transaction completes when the bounded task flow exits.
Always Use Existing Transaction: When called, the bounded task flow participates in an existing transaction already in progress.
Use Existing Transaction if Possible: When called, the bounded task flow either participates in an existing transaction if one exists, or starts a new transaction upon entry of the bounded task flow if one doesn't exist.
Commit and Rollback must be specified for 'Always Begin New Transaction' and 'Use Existing Transaction if Possible'.
No comments:
Post a Comment