Paco:
I'm having difficutly in understanding how WS-Addressing is useful at
all to anything other than SOAP.
[ SOAP Payload ] == message, transfer mechanism TBD
[ SOAP Payload + WS-Address ] == message ready to go on some underlying
network protocol
Versus say:
[ CORBA payload + IIOP info ] == message ready to go via TCP
Or
[ XML payload + HTTP headers] == message ready to go via HTTP
So I see that other transfer protocols have addressing information as
part of their unit of transfer by default. SOAP doesn't have that, hence
the need for a SOAP-friendly addressing mechanism. So I am a little
puzzled as to how WS-Addressing is useful outside the SOAP domain. Can
you exemplify something from your experience to help?
As for WSDL being so "flexible," well that sure goes some way to
explaining how complex it is. Had WSDL gone down the route of describing
SOAP message exchanges, then I don't think we would have all be
thoroughly entertained by Rich's recent article. Perhaps Rich will
commit to a similar article on WS-Addressing if it becomes all-embracing
rather than focussed and useful :-)
Jim