W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

RE: WS-Addr issues

From: Savas Parastatidis <Savas.Parastatidis@newcastle.ac.uk>
Date: Fri, 5 Nov 2004 01:06:48 -0000
Message-ID: <37E80E80B681A24B8F768D607373CA800172C86D@largo.campus.ncl.ac.uk>
To: <public-ws-addressing@w3.org>

Hey Dave,

[snip[

>WSAddressing, through the mandated use of
> wsa:Action, has opened the door for that to change.  Newer specs,
> like WS-MDEX, have embraced wsa:Action's "I'm the operation"
definition
> to the point where if there are no parameters they don't even see the
need
> to put anything in the env:Body.  wsa:Action is no longer just an
> extension
> element but rather can be "the payload".  

To further add to Dave's above comment...

Due to the combination of wsa:action and reference properties we see
SOAP messages that look more and more like this...

<soap:Envelope>
  <soap:Header>
    <wsa:Action>blabla:SendEmailNotification</wsa:Action>
    <appl:CustomerFirstName>Savas</appl:CustomerFirstName>
    <appl:CustomerLastName>Parastatidis</appl:CustomerLastName>
  </soap:Header>
  <soap:Body />
</soap:Envelope>

Effectively moving the application-specific payload to the header
section of the soap envelope not leaving anything for the receiving
application specific actor.

Regards,
.savas.
Received on Friday, 5 November 2004 01:06:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:59 GMT