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

RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!)

From: Christopher B Ferris <chrisfer@us.ibm.com>
Date: Tue, 23 Nov 2004 11:28:50 -0500
To: "Srinivas, Davanum M" <Davanum.Srinivas@ca.com>
Cc: "Glen Daniels" <gdaniels@sonicsoftware.com>, "Martin Gudgin" <mgudgin@microsoft.com>, public-ws-addressing@w3.org, public-ws-addressing-request@w3.org
Message-ID: <OF00380938.3A15451F-ON85256F55.005A07A3-85256F55.005A87D4@us.ibm.com>

Dims,

You wrote:

> This situation is because there is NO way
> to distinguish between regular soap headers and reference properties and
> reference parameters.

And I maintain that is because there is no distinction to be made. An 
intermediary
is certainly free to inspect (not process in the SOAP sense) headers in 
the messages
it receives and forwards, but again, there is no distinction between a 
SOAP header block
added because it was a ref prop/param or one that was added for some other 
purpose
such as in support of a QoS protocol such as WS-Reliable Messaging or 
WS-Addressing.

A SOAP header block is a SOAP header block. The thing that distinguishes 
it from other
SOAP header blocks is its QName and the value of the soap:role/actor 
attribute.

Cheers,

Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog: http://webpages.charter.net/chrisfer/blog.html
phone: +1 508 377 9295

public-ws-addressing-request@w3.org wrote on 11/23/2004 10:20:19 AM:

> 
> Summarizing (for my own benefit):
> Suppose there is a .NET shop with an application already deployed and
> working with a combination of RefProp's and RefParam's and they want to
> install a web service management solution (proxy-based?) that monitors
> the Addressing thingies flowing through the system, they have to
> manually enter ALL the Qname's for ALL the RefProp's and RefParam's in
> their (already existing and working!) system AND THEN they will be able
> to monitor what's happening. This situation is because there is NO way
> to distinguish between regular soap headers and reference properties and
> reference parameters.
> 
> -- dims
> 
> -----Original Message-----
> From: Martin Gudgin [mailto:mgudgin@microsoft.com] 
> Sent: Tuesday, November 23, 2004 9:52 AM
> To: Srinivas, Davanum M; Christopher B Ferris
> Cc: Glen Daniels; public-ws-addressing@w3.org;
> public-ws-addressing-request@w3.org
> Subject: RE: Sample SOAP message on the wire with Reference Properties
> and Parameters (without a wrapper!)
> 
> Personally, I'd just use different Qnames.
> 
> Gudge 
> 
> > -----Original Message-----
> > From: public-ws-addressing-request@w3.org
> > [mailto:public-ws-addressing-request@w3.org] On Behalf Of Srinivas, 
> > Davanum M
> > Sent: 23 November 2004 14:45
> > To: Christopher B Ferris
> > Cc: Glen Daniels; public-ws-addressing@w3.org; 
> > public-ws-addressing-request@w3.org
> > Subject: RE: Sample SOAP message on the wire with Reference Properties
> 
> > and Parameters (without a wrapper!)
> > 
> > 
> > RefParams and RefProps are used for 2 different things and we don't 
> > want to know which one is which?????? If I am a management proxy and 
> > my user wants to track only RefParams for his web service endpoint, i 
> > should be able to do that without asking my user to type in the 
> > Qname's for each RefParam?
> > 
> > -- dims
> > 
> > -----Original Message-----
> > From: Christopher B Ferris [mailto:chrisfer@us.ibm.com]
> > Sent: Tuesday, November 23, 2004 9:36 AM
> > To: Srinivas, Davanum M
> > Cc: Glen Daniels; public-ws-addressing@w3.org; 
> > public-ws-addressing-request@w3.org
> > Subject: RE: Sample SOAP message on the wire with Reference Properties
> 
> > and Parameters (without a wrapper!)
> > 
> > It is irrelevant. It is assumed that the endpoint that receives these 
> > SOAP header blocks knows why it put them in the EPR in the first 
> > place.
> > There is no need to distinguish which were ref props and which were 
> > ref params in the EPR.
> > 
> > Cheers,
> > 
> > Christopher Ferris
> > STSM, Emerging e-business Industry Architecture
> > email: chrisfer@us.ibm.com
> > blog: http://webpages.charter.net/chrisfer/blog.html
> > phone: +1 508 377 9295
> > 
> > 
> > 
> > "Srinivas, Davanum M" <Davanum.Srinivas@ca.com> Sent by:
> > public-ws-addressing-request@w3.org
> > 11/23/2004 09:26 AM
> > 
> > To
> > "Glen Daniels" <gdaniels@sonicsoftware.com> cc 
> > <public-ws-addressing@w3.org> Subject
> > RE: Sample SOAP message on the wire with Reference Properties and 
> > Parameters (without a wrapper!)
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Next question, when you get a soap message on the wire with "four 
> > other random headers" how do you distinguish that a few of them are 
> > RefProp's and others are RefParam's? See my point?
> > 
> > -- dims
> > 
> > -----Original Message-----
> > From: Glen Daniels [mailto:gdaniels@sonicsoftware.com]
> > Sent: Tuesday, November 23, 2004 8:21 AM
> > To: Srinivas, Davanum M
> > Cc: public-ws-addressing@w3.org
> > Subject: RE: Sample SOAP message on the wire with Reference Properties
> 
> > and Parameters (without a wrapper!)
> > 
> > 
> > > Does anyone have a Sample SOAP message on the wire with Reference 
> > > Properties AND Parameters (without a wrapper element!)?
> > 
> > Uh, sure - pick any SOAP message with <wsa:To>, <wsa:Action>, and 
> > let's say four other random headers.  You can then construct EPRs 
> > which have those other headers as either RefProps or RefParams. 
> > Voila.
> > 
> > --Glen
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> 
Received on Tuesday, 23 November 2004 16:29:27 GMT

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