Hi Benjamin,
Then you call the participate(String soapMsg, String id) of the TXWS
sending a common SOAP message of, for example a common debit operation.
With help of the id the TXWS loads the TransactionImpl of the map and
resumes the Transaction (by calling resume() on the
TransactionManagerImpl). It takes the SOAP messages and enhances it with
the coordination context by calling:
If I understood right what you are trying to do, this is not how that
should be done.
Kandula automatically begins and resumes transactions, even if they span
multiple threads or hosts: as soon as a SOAP message comes in, it is
(automatically! that's why you need to modify the server-config.wsdd
file) scanned for transaction headers. If found, the given transaction
is resumed for the current thread.
but the only problem is that the last ">"
which closes the Envelope tag is not there.
Do you use (or have in the classpath) the STAX Parser bundled with Axis2
0.92? Please have a look at http://issues.apache.org/jira/browse/AXIS2-290
Is my project realizable at all with kandula? I think there is maybe a
problem that the transaction is spanning several threads (Everytime
there is an operation on the TXWS there is a new one an there is one for
my client).
Yes, that can be done with kandula - keep in mind that everything that
relates to handling, creation, registration etc of transactions is
handled by kandula automatically. You just need to implement your
business logic, and the first service that decides to use a transaction
must call tm.begin() before calling any other service. Running
transactions will - if your handlers are deployed right - automatically
propagated to any other web service you call.
HTH
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
