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 to put the transport address you're sending the message to in the wsa:To.
All that said, if you want to raise a JIRA about the fact that the Axis2 WS-A Handlers don't process soap role/actor attributes, (I think a different scenario than you're talking about) I'd be willing to take a look. Cheers, David [1] http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/#soaphdrvtransport On 26/10/2007, Brian De Pradine <[EMAIL PROTECTED]> wrote: > > 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 intermediary a bit > pointless. > > Anyone else care to chime in? > > Cheers > > Brian DePradine > Web Services Development > IBM Hursley > External +44 (0) 1962 816319 Internal 246319 > > If you can't find the time to do it right the first time, where will you > find the time to do it again? > > > "Erwin Reinhoud" <[EMAIL PROTECTED]> wrote on 25/10/2007 15:54:10: > > > > 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); > > > > The ops.setTo value will be used to dispatch the message. > > > > > > Kind regards, > > Erwin > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > ________________________________ > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > > > > > > > -- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
