Quoting Benjamin Schmeling <[EMAIL PROTECTED]>:
> resumes the Transaction (by calling resume() on the
> TransactionManagerImpl). It takes the SOAP messages and enhances it with
> the coordination context by calling:
>
> SOAPHeader header = message.getSOAPEnvelope().getHeader();
> tx.getCoordinationContex().toSOAPHeaderElement(header);
why do you have to call resume if you are directly serializing the coordination
context into the message? an alternative is to have the proxy (TXWS) use the tm
to add in the context-- say if you have a debit(acc#, amt) method in the actual
service, the proxy would have a method (stub) like
debit(txid, acc#, amt) {
tx = get(txid)
tm.resume(tx);
r = debit(acc#, amt)
tm.suspend(tx);
return r;
}
also keep in mind that kandula uses reference properties. so you need to copy
those as well when you forward a messages.
> which closes the Envelope tag is not there. When I look at the message
> with debugging, this ">" is definetly existing. The same occurs in the
> followed registration message. There is no response and no error.
try adding the missing > manually and resending the message. also the
addressing handler reroutes any replies with a reply-to element using another
connection.
are you using both TxHandlers (*.coordinator.at./*.geronimo.*)
at the same time? this will not work and there shouldn't be a need to do so
either.
> 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).
multiple threads is not an issue.
thanks,
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
