U r right. This seems to be a bug. Let me look into this.
Chamikara
On 8/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:
Hi there,
I am working with the latest version of Sandesha2.
The problem that I run into is that the WS-Addressing Action header element is changed to
urn:annonOutInOp from the second message in a sequence.
So the first message keeps the WS-Addressing Action header element as I specified it with
options.setAction("action"); but from the second message automatically the Action element
is replaced with urn:annonOutInOp. When I run the SyncPingClient of the Sandesha2 samples
the action remains "urn:wsrm:Ping" for every message in the sequence. However in the
SyncEchoClient of the Sandesh2 samples the same think occurs as I get, the action element
is changed to urn:annonOutInOp.
To be able to use the WS-Addressing capabilities of Axis2 to my opinion the Action element
should remain as it was set at first, just like the SyncPingClient.
How do you think about this?
Thanks,
Tijs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
