21 information includes, for example, passing directives or contextual information related to
the processing of the message. This allows a SOAP message to be extended in an application-specific manner.
Each header-blocks element may contain attributes that apply to each of the enclosed header blocks.
9.3.3.6 mustUnderstand
If true, means that the targeted SOAP node must process the block according to the specification of that block. Such a block is colloquially referred to as a mandatory header
block. In fact, processing of the SOAP message must not even start until the node has identified all the mandatory header blocks targeted at itself, and understood them.
Understanding a header means that the node must be prepared to do whatever is described in the specification of that block. Keep in mind that the specifications of
header blocks are not a part of the SOAP specifications.
9.3.3.7 relay
SOAP 1.1: Not Applicable SOAP 1.2: Indicates whether a header block targeted at a SOAP intermediary must be
relayed if it is not processed. Note that if a header block is processed, the SOAP processing rules require that it be
removed from the outbound message. It may, however, be reinserted, either unchanged or with its contents altered, if the processing of other header blocks determines that the
header block be retained in the forwarded message. The default behavior for an unprocessed header block targeted at a role played by a SOAP intermediary is that it must
be removed before the message is relayed.
9.3.3.8 role
Identifies the role played by the intended target of that header block. A SOAP node is required to process a header block if it assumes the role identified by this attribute. How a
SOAP node assumes a particular role is not a part of the SOAP specifications.
In SOAP 1.1 it will be used to fill the actor attribute: The SOAP actor global attribute can be used to indicate the recipient of a header element. The value of the SOAP actor
attribute is a URI. The special URI http:schemas.xmlsoap.orgsoapactornextindicates that the header element is intended for the very first SOAP application that processes the
message.
The value may be set to a URI value, or to one of the short names in the list below:
22
Copyright © 2009 Open Geospatial Consortium, Inc.
Ver Short-name URI
1.1 next http:schemas.xmlsoap.orgsoapactornext
1.2 next http:www.w3.org200305soap-enveloperolenext
1.2 none http:www.w3.org200305soap-enveloperolenone
1.2 ultimateReceiver http:www.w3.org200305soap-enveloperoleultimateReceiver
9.3.3.9 Header Block Element