Copyright © 2006 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 is the First Public Working Draft of the SOAP 1.2 Part 3: One-Way MEP document. It has been produced by the XML Protocol Working Group which is part of the Web Services Activity. The current intention of the Working Groups is to issue the final version of this specification as a Working Group Note.
Comments on this document are welcome. Please send them to the public mailing-list xmlp-comments@w3.org (archive). It is inappropriate to send discussion email to this address.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. The group does not expect this document to become a W3C Recommendation. 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.
Publication as a Working Draft 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.
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 is limited to transmission of (nearly) identical messages from one sending node to zero or more receiving SOAP node(s); typically, in the case of multiple receivers, the messages differ only in their destinations. Implementations MAY choose to support multiple meps at the same time.
| Editorial note | |
| The XML Protocols Workgroup solicits feedback on the question of whether this MEP should indeed provide support for transmission to more than one receiver, as described in this draft, or whether it should speak only of a single sender, a single receiver, and a single message. | |
The sending node MUST send 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. The sender is not required to detect whether transmission succeeds or fails, but the sender SHOULD fault in a binding specific manner if it discovers that transmission is unsuccessful.
A receiving node MUST determine whether a given message is successfully received, and if so, 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). Determination of success by a receiver MAY be conservative, I.e. a receiver may in exceptional circumstances treat as erroneous or lost a message which is 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 declared in error (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.)
Abnormal operation during a one-way message exchange might be caused by a failure to transfer the message or a failure at a receiving SOAP node to process the message. Such failures might be silent at either or all of the sending and recieving SOAP nodes involved, or might result in the generation of a SOAP or binding-specific fault (see 2.4 Fault Handling). Also, during abnormal operation each SOAP node involved in the message exchange might differ in its determination of the successful completion of the message exchange.
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 |
There may be other properties related to the operation of the message exchange and are processed according to their own feature specifications.
| 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. |