The embodiment of the processing logic necessary to transmit, receive, process and/or relay a SOAP message, according to T He set the conventions defined by this recommendation. A SOAP node is responsible to enforcing the rules that govern the exchange of SOAP messages (2. SOAP processing Model). It accesses the services provided by the underlying protocols through one or more SOAP bindings.
SOAP role
A SOAP receiver ' s expected function in processing a message. A SOAP Receiver can act in multiple roles.
Understand
SOAP node is a real-world node that can handle SOAP messages, and SOAP node is a physical concept; SOAP role is a logical concept in which SOAP node plays a part when handling SOAP messages. A SOAP node can act as multiple soap roles, and a soap role can be played by multiple soap node.
1. Determine the set of roles in which the node was to act. The contents of the SOAP envelope, including any SOAP header blocks and the SOAP body, May is inspected in making such Ermination.
2. Identify all header blocks targeted in the node that are mandatory.
3. If one or more of the SOAP header blocks identified on the preceding step are not understood by the node then gene Rate a single SOAP fault with the Value of Code set to "Env:mustunderstand" (Click 5.4.8 SOAP mustunderstand faults). If such a fault is generated, the any further processing must the not are done. Faults relating to the contents of the "SOAP body" must not being generated in this step.
4. Process all mandatory SOAP header blocks targeted on the node and, in the case of a ultimate soap receiver, the S OAP body. A SOAP node may also choose to process non-mandatory SOAP header blocks targeted at it.
5. In the "case of" a soap intermediary, and where the SOAP message exchange pattern and results of processing (e.g. no Fault generated) require the SOAP message is sent further along the SOAP message path, relay the ' message as describe D in section 2.7 relaying SOAP Messages.
Four relaying soap Messages (relayable SOAP header blocks)
Role
Header Block
Short-name
Assumed
Understood & processed
Forwarded
Next
Yes
Yes
No, unless reinserted
No
No, unless relay = "true"
user-defined
Yes
Yes
No, unless reinserted
No
No, unless relay = "true"
No
N/A
Yes
UltimateReceiver
Yes
Yes
N/A
No
N/A
None
No
N/A
Yes
Understand
The so-called relaying SOAP message (SOAP replay) only handles a header block in SOAP node, but ignores the header because it cannot understand the header block (can ' t understand) Block is meaningful, (this header block does not set MustUnderstand to true, otherwise it is not understandable to return a soap Fault, instead of continuing to pass the SOAP message forward, there is no relay meaning). If the relay property of the header block is true, then soap node must keep the header block in the SOAP message and forward it to the next soap node.
In summary, SOAP message replay is only meaningful for the SOAP intermediate node (SOAP intermediary) and is meaningful only if the intermediate node cannot handle a header block that needs to be processed by it but has not set the MustUnderstand property to True. The header block will be kept in the SOAP message and forwarded forward to the next soap node.
SOAP messages generated by the five soap intermediate nodes
The SOAP intermediate node must process the SOAP message it receives as described in Part three and generate a new SOAP message in the following manner and pass it forward to the next soap node.
Remove all processed SOAP header blocks.
Remove all non-relayable SOAP header blocks that were targeted at the forwarding node but ignored during.
Retain all relayable The SOAP header blocks this were targeted at the forwarding node but ignored during.
Insert or reinsert some header blocks if the soap intermediary determined to does that. The header blocks that were inserted or reinserted might is indistinguishable from one or more of the header blocks remove D by the intermediary. Processing is defined this terms of re-inserting header blocks (rather than leaving them in place) to emphasize the Nee D to process them at each SOAP node along the SOAP message path.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
