RE: axis2 1.3 wsa:To header usage

2007-10-31 Thread Erwin Reinhoud
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: axis-user@ws.apache.org Onderwerp: Re: axis2 1.3 wsa:To header usage On 10/25/07, Erwin Reinhoud

RE: axis2 1.3 wsa:To header usage

2007-10-31 Thread Erwin Reinhoud
: axis2 1.3 wsa:To header usage Sure, The WS-A WG didn't really define much on the mlti-hop scenario so the specifications don't help much here. It is worth pointing out that in the interops we did, it became apparent that SOAP Binding 3.5 [1] was interpreted by different people in different ways

Re: axis2 1.3 wsa:To header usage

2007-10-30 Thread Amila Suriarachchi
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

Re: axis2 1.3 wsa:To header usage

2007-10-29 Thread David Illsley
Sure, The WS-A WG didn't really define much on the mlti-hop scenario so the specifications don't help much here. It is worth pointing out that in the interops we did, it became apparent that SOAP Binding 3.5 [1] was interpreted by different people in different ways, and that the 'safest' route is

Re: axis2 1.3 wsa:To header usage

2007-10-26 Thread Brian De Pradine
Hello Erwin, The thing about intermediaries is that they are usually there to hide the address of the of the ultimate receiver ( imagine a gateway server or proxy for instance ). In that case flowing the address of the ultimate receiver across the intermediary would tend to make having the

axis2 1.3 wsa:To header usage

2007-10-25 Thread Erwin Reinhoud
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