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

RE: WS-Addr issues

From: Francisco Curbera <curbera@us.ibm.com>
Date: Thu, 4 Nov 2004 21:33:22 -0500
To: "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>
Cc: public-ws-addressing@w3.org, public-ws-addressing-request@w3.org
Message-ID: <OFF19F9F90.C39419CD-ON85256F43.000D7DE8-85256F43.000E0AC9@us.ibm.com>

You can already do that w/o reference properties. It seems that your
example tries to show that application data can be encoded in message
headers as opposed to the body. Well, SOAP already allows you to do that if
that is what you wish to do. However, that example has nothing to do with
reference properties, which can never stand for input parameters. Input
parameters encode requester data sent to the service endpoint, whereas the
value of reference properties is fixed by the service provider. Clients
only echo them back.


                      "Savas Parastatidis"                                                                                                      
                      <Savas.Parastatidis@newca        To:       <public-ws-addressing@w3.org>                                                  
                      stle.ac.uk>                      cc:                                                                                      
                      Sent by:                         Subject:  RE: WS-Addr issues                                                             
                      11/04/2004 08:06 PM                                                                                                       

Hey Dave,


>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"
> to the point where if there are no parameters they don't even see the
> 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:Body />

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

Received on Friday, 5 November 2004 04:23:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:07 UTC