RE: NEW ISSUE; wsa:To interaction with application protocols

Hi Mark!
i think this is closely related to issue 6 "Message Property Optionality":

AIUI you'd like an addressing xxTo: value to map to an populate a transport 
xxTo: value, whereas Marc is suggesting that a missing addressing xxTo: 
could default to to a value derrived from the transport.
i guess both issues raise an issue with the way the spec is structured given 
that the SOAP and WSDL bindings are thus far "transport-neutral". 

 -----Original Message----- 
 From: on behalf of Mark Baker 
 Sent: Mon 13/12/2004 15:17 
 Subject: NEW ISSUE; wsa:To interaction with application protocols

 The SOAP binding currently only supports uses of SOAP which treat
 underlying application protocols as transport protocols.  It does this
 by requiring that a wsa:Address EII map to the wsa:To SOAP header,
 rather than providing for the possibility of mapping to the identifier
 in the underlying protocol.  The spec says;
   "The [address] property in the endpoint reference is copied in the
    [destination] message information property. The infoset
    representation of the [destination] property becomes a header block
    in the SOAP message."
 As an example of the problem, consider the following EPR (an edited
 version of one from the spec);
 <wsa:EndpointReference xmlns:wsa="..." xmlns:fabrikam="...">
 Here, "foobar@fabrikam123.example" is required to go in the SOAP header,
 rather than in the "RCPT TO" command of the SMTP protocol (as an example
 of one email delivery protocol).
 I think the shortcoming will significantly hamper the ability for
 WS-Addressing enabled agents and services to integrate with existing
 applications on the Internet, such as email, instant messaging, and the
 Mark Baker.   Ottawa, Ontario, CANADA.


Received on Monday, 13 December 2004 19:42:54 UTC