Re: MustUnderstand and WS-Routing

Doug Ransom wrote:
> In WS-Routing,
> The path element contains a mustUnderstand attribute from the soap
> envelope namespace http://schemas.xmlsoap.org/soap/envelope/ . The WS-
> Routing Spec indicates this value must be 1 or true.  What will happen
if
> one sets it to 0 and fires it off to:
> - a SOAP processor unaware of WS-Routing?
> - A WS-Routing aware SOAP processor?


From spec section 7.4
"When a WS-Routing message is carried within an HTTP message there is no
mechanism for guaranteeing that there is a WS-Routing receiver at the
destination of the HTTP message. In order to ensure that a SOAP
processor honors the WS-Routing semantics, a WS-Routing sender sending a
WS-Routing message using HTTP SHOULD mark the WS-Routing header with a
SOAP mustUnderstand attribute with a value of "1" (see [15] section
4.2.3) and a SOAP actor attribute with a value of
"http://schemas.xmlsoap.org/soap/actor/next" (see [15] section 4.2.2)"


The spec says 'SHOULD' but I would argue that the ultimate destination
may or may not honor WS-R semantics and still be viable.  It would be
difficult to imagine a world where intermediaries + services would be
totally dependent of WS-R (makes no sense to me).  Therefore, I would
believe that an intermediary sending WS-R to the ultimate destination
should make the MU="0" in that manner the UD can choose process WS-R or
not.

Thx,

-Matt Long
Phalanx Systems, LLC

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.