Hello Amila,
Thanks very much this works.
Kind regards,
Erwin
-----Oorspronkelijk bericht-----
Van: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 30 oktober 2007 10:40
Aan: [email protected]
Onderwerp: Re: axis2 1.3 wsa:To header usage
On 10/25/07, Erwin Reinhoud < [EMAIL PROTECTED]> wrote:
Hello all,
Don't know if this is the correct location to post this, so please let me know
if not.
I create a client and want to make a call with WS-Addressing headers. What i
noticed is that often there is a strong relation between the wsa:To value and
the actual http uri being used to send the message to the next hop. I thought
the wsa:To could contain the (logical) value of the end destination. So if
there are two intermediairies than the wsa:To can stay the same over all hops.
Currently this does not seem to be. Is my perception of the wsa:To wrong?
ServiceClient client = new ServiceClient(context,null);
Options ops = new Options();
Endpointreference to = new Endpointreference("finalDest");
ops.setTo(to);
Endpointreference epr = new Endpointreference("
http://localhost/axis2/services/myservice";);
client.setoptions(ops);
client.setTargetEpr(epr);
try like this
client().getOptions().setProperty( Constants.Configuration.TRANSPORT_URL,
"
http://localhost:8085/WSAddressingCR_Service_WCF/WSAddressing10.svc/Soap11
<http://localhost:8085/WSAddressingCR_Service_WCF/WSAddressing10.svc/Soap11>
");
Amila.
The ops.setTo value will be used to dispatch the message.
Kind regards,
Erwin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi,
WSO2 Inc.
