Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document is a Working Group Note of the W3C. It has been produced by the XML Protocol Working Group, which is part of the Web Services Activity.
As of the publication of this Working Group Note the XML Protocol Working Group has completed work on this document. Major changes to this specification can be found in the Changelog. Please report errors in this document to the public mailing list xmlp-comments@w3.org (archive). It is inappropriate to send discussion email to this address.
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
A list of current W3C Recommendations and other technical reports can be found at http://www.w3.org/TR.
1 Introduction
1.1 Notational Conventions
2 SOAP One-way Message Exchange Pattern
2.1 SOAP Feature Name
2.2 Description
2.3 Property Description
2.4 Fault Handling
3 References
3.1 Normative References
3.2 Informative References
A Change Log (Non-Normative)
SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC 2119].
With the exception of examples and sections explicitly marked as "Non-Normative", all parts of this specification are normative.
This section defines the message exchange pattern (MEP) called "One-way". The description is an abstract presentation of the operation of this MEP. It is NOT intended to describe a real implementation or to suggest how a real implementation should be structured.
This message exchange pattern is identified by the URI (see SOAP 1.2 Part 1 [SOAP Part 1] SOAP Features):
"http://www.w3.org/2006/08/soap/mep/one-way/"
The SOAP One-way MEP defines properties for the exchange of a SOAP message. In the absence of failure in the underlying protocol, this MEP consists of zero or more SOAP messages. The scope of a one-way MEP instance is limited to transmission of messages from one sending node to zero or more receiving SOAP node(s). The ImmediateSender and ImmediateDestination properties may differ among nodes. The envelope in the InboundMessage property at each successful receiver SHOULD be identical to the envelope in the OutboundMessage at the sender. Implementations MAY choose to support multiple MEPs at the same time.
The sending node MUST attempt to send, in a binding-specific manner, the SOAP Message provided in http://www.w3.org/2003/05/soap/mep/OutboundMessage to the node(s) identified by http://www.w3.org/2003/05/soap/mep/ImmediateDestination. If the sender has a means of detecting successful or unsuccessful transmission, it SHOULD fault in a binding-specific manner in the event that transmission failure is detected.
When a message is successfully received by a SOAP node, that node MUST populate http://www.w3.org/2003/05/soap/mep/InboundMessage with the received message and MUST process the message in http://www.w3.org/2003/05/soap/mep/InboundMessage according to the SOAP Processing Model (see SOAP 1.2 Part 1 [SOAP Part 1]Processing SOAP messages). A receiver MAY (though typically only in exceptional circumstances) treat as erroneous, or lost, a message that has been received intact. Typical reasons for making such decisions might include shortage of buffer space, network interface overruns, etc.. A receiver MAY fault in a binding-specific manner if some particular message is determined to have been unsuccessfully received (note, however, that in many cases where receipt is unsuccessful, information identifying the message or its sender may be unreliable, in which case there may be little if any value in reflecting a message-specific fault.)
The One-way MEP defines a set of properties described below.
| Property Name | Property Description | Property Type |
|---|---|---|
http://www.w3.org/2003/05/soap/mep/InboundMessage
| An abstract structure that represents the current inbound message in the message exchange. This abstracts both SOAP Envelope and any other information structures that are transferred along with the envelope. This property is populated if and only if the message is successfully received. | Not specified |
http://www.w3.org/2003/05/soap/mep/OutboundMessage
| An abstract structure that represents the current outbound message in the message exchange. This abstracts both SOAP Envelope and any other information structures that are transferred along with the envelope. | Not specified |
http://www.w3.org/2003/05/soap/mep/ImmediateDestination
| The identifier of the immediate destination of an outbound message. (NOTE: the URI supplied MAY be the identifier of a single destination SOAP node, or MAY be the identifier of a multicast group, which itself consists of zero or more destination nodes. Whether multicast is supported is binding-dependent. This MEP specification provides no standard means for representing a multicast group, except to require that the group as a whole be designated by a URI.) | xs:anyURI |
http://www.w3.org/2003/05/soap/mep/ImmediateSender
| The identifier of the immediate sender of an inbound message. | xs:anyURI |
This MEP MAY be extended by later specifications. Such extensions MAY add additional properties to the ones listed above.
Each SOAP node involved in the message exchange makes its own determination of successful completion of the message exchange. Each node MAY independently signal a fault in the case of abnormal operation. Determination of successful operation and disposition of faults are outside the scope of this specification.
| Who | When | What |
|---|---|---|
| DBO | 20041208 | Initial Revision |
| DBO | 20060330 | 2nd Revision |
| DBO | 20060530 | Adding sending and receiver MUSTs |
| DBO | 20060720 | Update date parts, checked into cvs, and moved abnormal operation paragraph to end of 2.2 |
| DBO | 20060803 | Added InboundMessage property and text about populating, removed State property, other minor edits. Moved to xmlspec 2.10 dtd and xmlspec.xsl 1.54 (2005/10/13) |
| DBO | 20060809 | Removed failureReason property, explicit support for multicast by saying 0 or more nodes, changing "the receiver" to "a receiver" etc. |
| DBO | 20060830 | Some more clarifications on multicast, added ednote for feedback. |
| DBO | 20070330 | Did Mutiple fixes based on WSDL WG comments. Minutes at http://www.w3.org/2007/03/21-xmlprotocol-minutes.html, WSDL Comments at http://lists.w3.org/Archives/Public/xmlp-comments/2007Feb/0000.html. WG made decisions about 1, 5, 10, 11. Items 2,3 done at editors discretion. |
| DBO | 20070425 | Did 2 fixes, http://www.w3.org/Bugs/Public/show_bug.cgi?id=4404, http://www.w3.org/Bugs/Public/show_bug.cgi?id=4407. Minutes at http://www.w3.org/2007/04/25-xmlprotocol-minutes.html. Also removed Ed note. |
| DBO | 20070516 | Did 2 fixes, first 2 of Noah's comments from 5/4/2007 and moved error handling out of 2.2 |