Raymond Feng wrote:
Hi,
I propose to add the following to the BigBank scenario too to cover
transaction policies and JMS binding.
1) Have separate components to represent the SavingsAccountService and
CheckingAccountService. The two services will be backed by two different
resource managers (Database or JMS queue). Please see the code at [1]
and diagrams at [2].
2) Add a TransferService to transfer money between accounts. The
operations will be executed in a global transaction.
3) The TransferService will be exposed over binding.jms. The request of
money transfer from the web front will be served by the TransferService
over JMS.
[1]
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/itest/transaction
[2]
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Transaction+Intents+and+Policies
Thanks,
Raymond
Sounds good to me. The other aspect that this scenario will allow us to
explore is interaction between the JMS binding and databindings (as
Bigbank flows complex types).
I'd suggest to work on these two versions of Bigbank in parallel in
different modules:
a) secure bigbank with security policies
b) reliable transfers with JMS and transactions
i.e. two different copies of BigBank.
And then bring the two together at some point later.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
