I have gone through some of the articles on ws-addressing, but couldn't actually figure out why ws-addressing is required ?
what I understand from ws-addressing is that using ws-addressing a response can be addressed to some other destination. For e.g. client-A
invokes a service at Server1 and requires the response to be sent to Client-B. ws-addressing provides the standarized <wsa:ReplyTo> MI
header to achieve this. The client client-A will send a SOAP message with <wsa:ReplyTo> element containing the url of destination endpoint
where response is to be made, in SOAP header. The server when find <wsa:ReplyTo> element in SOAP header, will send the response to the
Similarly From header is to send the acknowledgement back to the sender & FaultTo to send the fault to sender/other fault handler.
Utility of EPR's (End Point Reference) is also vague.
Is this the only scenario where ws-addressing should be implemented ?
Comments/Suggestions are welcome.
WS-Addressing basically establishes a standard way of specifying "alternate contacts" for such a dynamic landscape.
SOAP allows for an entire chain of SOAP nodes to "process" a single SOAP request. It starts at the initial SOAP sender, goes over any number of SOAP intermediaries, and then ends up at the ultimate SOAP receiver.
what are SOAP intermediaries ? Talking at the implementation level Is this a kind of service or a firewall ?
In some cases the SOAP sender may only be aware of the first intermediary the message is sent to, and the message is then dynamically routed (potentially through multiple SOAP nodes) based on content of the message; so some of the intermediaries may not know who the initial Sender is. Sometimes the SOAP message may be sent on another systems behalf and when "certain things happen" yet other systems need to be notified.
Can we have some practical example of this. That will make the thing more clear.