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 13:01:55 -0500
Message-ID: <87527035FDD42A428221FA578D4A9A5B086CF6B8@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>

Found a sample with both Prop's and Param's
(http://www.informit.com/guides/printerfriendly.asp?g=xml&seqNum=150)

I guess the bottom line is...Though it may make life easier for some
folks if we have wrapper elements (being able to distinguish between
regular soap headers, RefParam's and RefProp's) there's a down-side. in
Chris's words we "lose the ability to leverage the SOAP processing
model". 

Looks like we have to wait for the other 2 related threads to start
(http://www.w3.org/2002/ws/addr/wd-issues/)
i008   	  Glen Daniels   RefProps/RefParams as individual SOAP headers
i007   	  Marc Hadley    Processing model of headers

Since if we have our own processing model.....(and/or) maybe make
wrappers optional?

-- dims

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

Because if Ref Props are different, it implies that two EPRs have
different metadata (portType, security etc.) Whereas if only ref parmas
differ, it implies the same metadata.

Gudge

> -----Original Message-----
> From: Srinivas, Davanum M [mailto:Davanum.Srinivas@ca.com]
> Sent: 23 November 2004 16:33
> To: Christopher B Ferris
> Cc: Glen Daniels; Martin Gudgin; 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!)
> 
> Hmm...if I buy that, then as Rich points out in prev email, since we 
> can't make a distinction why have 2 bags? Prop's and Param's?
> 
> -- dims
> 
> -----Original Message-----
> From: Christopher B Ferris [mailto:chrisfer@us.ibm.com]
> Sent: Tuesday, November 23, 2004 11:29 AM
> To: Srinivas, Davanum M
> Cc: Glen Daniels; Martin Gudgin; 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!)
> 
> Dims,
> 
> Why? There is no utility in making such a distinction from the 
> perspective of a received message, they are simply SOAP header blocks 
> that are processed in the usual manner using the SOAP processing 
> model.
> 
> There is utility in making the distinction when populating an EPR, but

> not in processing the resultant header blocks upon receipt of a 
> message that has been sent to the endpoint referenced.
> 
> 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:42 AM
> 
> To
> "Martin Gudgin" <mgudgin@microsoft.com>, "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!)
> 
> 
> 
> 
> 
> 
> 
> Martin,
> 
> Am the guy writing the ws-addressing implementation here
> (http://ws.apache.org/ws-fx/addressing/) which works with Axis 
> (http://ws.apache.org/axis/). I need to pick the RefProp's and 
> RefParam's put them in 2 different collections within an addressing 
> datastructure for obvious reasons.
> 
> -- dims
> 
> -----Original Message-----
> From: Martin Gudgin [mailto:mgudgin@microsoft.com]
> Sent: Tuesday, November 23, 2004 9:34 AM
> To: Srinivas, Davanum M; Glen Daniels
> Cc: public-ws-addressing@w3.org
> Subject: RE: Sample SOAP message on the wire with Reference Properties

> and Parameters (without a wrapper!)
> 
> Who is 'you' in the question below? 
> 
> 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:26
> > To: Glen Daniels
> > 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 18:02:27 GMT

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