Dasarath Weeratunge schrieb:
Quoting Benjamin Schmeling <[EMAIL PROTECTED]>:
also keep in mind that kandula uses reference properties. so you need to
copy
those as well when you forward a messages.
calling
SOAPHeader header = message.getSOAPEnvelope().getHeader();
tx.getCoordinationContex().toSOAPHeaderElement(header);
seems to be enough.
yes, this should be the case. reference properties are only used when it is
required to identify the participant or the transaction where no additional
information is available in the message.
The problem was that when I enhanced the application message
"manually", there should not be a transaction handler in the request flow.
The ">" seems to be missing if the transaction handler cannot handle the
message.
could you please explain this a little? I'm just curious whether there is any
problem.
Okay,
when I call my participate(id, message) operation at the TXWS, I load my
TransactionImpl object from a map by using the id. Then I call:
SOAPHeader header = message.getSOAPEnvelope().getHeader();
tx.getCoordinationContex().toSOAPHeaderElement(header);
the modified message is passed back to the client.
Now when the client sends the modified application message, the
TransactionHandler seems to have problems with that message. The
TCPMonitor shows the application message lacking the ">" with no
response and no fault.
thanks,
--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]
