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