-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W-11599455 try scope revamp and ref duke #2386
base: v4.4
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
edits
|
||
The Try scope treats child operations as a transaction when the Transactional Action (`transactionalAction`) is set to `ALWAYS_BEGIN` or `BEGIN_OR_JOIN`. It can be configured in the following ways: | ||
//TODO: DO WE HAVE A LIST OF COMPONENTS AND OPERATIONS THAT SUPPORT TRANSACTIONS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, sort of, see "The only components that can define the transaction type are message sources (For example, jms:listener and vm:listener) and the Try scope." in https://docs.mulesoft.com/mule-runtime/4.4/transaction-management#transaction-types
|
||
== Error Handling with the Try Scope | ||
The Try scope enables transaction management and error handling for processing within the scope. xref:transaction-management.adoc[Transactions] force a group of processors to succeed or fail as a unit. The scope accepts xref:xa-transactions.adoc[Extended Architecture (XA)] and, by default, xref:single-resource-transaction.adoc[Local (LOCAL)] transactions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: move and consolidate details about the transaction types into the Transaction section.
Rolls back any transactions, then executes and uses that result to re-throw the existing error, causing its container Try scope's execution to fail. | ||
[source,xml,linenums] | ||
---- | ||
<try> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With implicit defaults for the transaction type and action (minus doc:id attribute):
With the attributes...
@@ -1,92 +0,0 @@ | |||
= Try Scope XML Reference |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to main page since it's so short.
Writer's Quality Checklist
Before merging your PR, did you: