Re: ISSUE 8 : "Clarity and Safety"

I have one question embedded below.

Martin Gudgin wrote:

>Glen,
>
>SOAP endpoints process headers ( and the body if they're the ultimate
>receiver ). They process these headers by looking at the QName and
>deciding whether they have software to process that QName.
>
>SOAP endpoints expect a given set of headers to be in messages they
>receive. In some cases this set will be empty. In other cases, it will
>include headers related to security, reliability etc. In still other
>cases it will include headers defined by WS-Addressing, possibly
>including headers inserted because an EPR contained
>ReferenceProperties/Parameters. However the sender decided to put a
>given set of headers in a message, the fact remains that they are
>headers the endpoint expects to be present. Whether they are Reference
>Properties/Parameters is immaterial. 
>
><snip>
>  
>

>SOAP headers can be targetted at different roles, marked as mandatory
>and (in the SOAP 1.2 case) marked for relaying if targetted at 'next'.
>
>Regarding EPRs, they are issued by some party, perhaps as part of some
>protocol exchange, perhaps in a WSDL document or something like it. Each
>EPR specifies the value of the wsa:To header and (optionally) the
>various Reference Properties/Parameters that are needed to address a
>message to a particular endpoint. The EPR issuer may choose to mark
>certain Reference Properties/Parameters for processing by a particular
>role/actor or mark certain headers for mandatory processing. 
>  
>
If a reference property header element is directed to any role other 
than ultimate distination, how is this
role identified in the EPR?  I would think reference properties are for 
the ultimate destination only.

Tom Rutt

>
>Gudge
>
>
>  
>

-- 
----------------------------------------------------
Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

Received on Monday, 15 November 2004 19:00:26 UTC