Thank you very much for your support (Hannes and Dasarath)
The example is really that what I needed and I got my Banking Service
working now. The only problem that remains is that the calling of the
commit() operation never returns. When I terminate my TestCase manually
and call it another time, there is a problem with the coordinator and
the transaction cannot be started again. How could I fix this?
TransactionManagerImpl tm =
TransactionManagerImpl.getInstance();
getBalance("1","DeutscheBankWS");
tm.begin();
sendDebit("20", "1","DeutscheBankWS");
sendCredit("20", "1","CommerzBankWS");
tm.commit(); <---
Thanks,
Benjamin
Quoting Hannes Erven <[EMAIL PROTECTED]>:
Hi Benjamin,
> * completionCoordinator is called and it returns no response
> (containing <Commit xsi:nil="true"
> xmlns="http://schemas.xmlsoap.org/ws/2004/10/wsat"/>)
> * participant is called and it returns no response
> * coordinator is called and it returns no response
> * completionInitiator is called and it returns no response
That's OK, since those calls aren't expected to return anything. The
"Commit" message just tells the coordinator to commit. Once it has, it
sends a message to the completionInitiator containing the result -
Commited or Rolled Back.
(The same pattern applies to the calls between participant ("prepare")
and coordintor.)
the reply to prepare can be either PREPARED or ABORTED. But both these messages
are sent over seperate connections. you should be able to them however.
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
