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: Srinivas, Davanum M <Davanum.Srinivas@ca.com>
Date: Tue, 23 Nov 2004 10:51:31 -0500
Message-ID: <87527035FDD42A428221FA578D4A9A5B086CF28A@usilms24.ca.com>
To: "Martin Gudgin" <mgudgin@microsoft.com>, "Christopher B Ferris" <chrisfer@us.ibm.com>
Cc: "Glen Daniels" <gdaniels@sonicsoftware.com>, <public-ws-addressing@w3.org>, <public-ws-addressing-request@w3.org>

Understood. Thanks.

-- dims 

-----Original Message-----
From: Martin Gudgin [mailto:mgudgin@microsoft.com] 
Sent: Tuesday, November 23, 2004 10:39 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!)

It depends on how the system is set up. If the EPRs also flow through
the same proxy, it could automatically record the Qnames of
RefProps/Params. Alternatively, if the endpoint holds the Qnames of Ref
Props/Params in a config file, the proxy could use that same config
file.

Gudge 

> -----Original Message-----
> From: Srinivas, Davanum M [mailto:Davanum.Srinivas@ca.com]
> Sent: 23 November 2004 15:20
> To: Martin Gudgin; 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!)
> 
> 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 15:51:32 GMT

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