This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Transaction Intents and Policies
Skip to end of metadata
Go to start of metadata

Transaction Intents and Policies


The scenario is a money transfer service offered in an online banking application. The customer can transfer money between accounts. The checking accounts are stored in a derby database and savings accounts are maintained in an ActiveMQ destinations.

Case 1 is a money transfer action between two resource managers under the
same global transaction. The 3 components are wired together locally using

Case 2 is an extended version where CheckingAccountService component is from
another composite. The TransferService component talks to the
CheckingAccountService over It will involve the
WS-AtomicTransaction and the server side should be able to import the
transaction and function as a XATerminator.