Copyright © 2006 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use, and software licensing rules apply.
SOAP Version 1.2 provides a request-response MEP and a response-only MEP. This, the SOAP One-way MEP, provides a one-way MEP.
This document is an editors' copy that has no official standing.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
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 provides a request-response MEP and a response-only MEP. This, the SOAP One-way MEP, 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/03/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 one SOAP message.
Abnormal operation during a one-way message exchange might be caused by a failure to transfer the message or a failure at the receiving SOAP node to process the message. Such failures might be silent at either or both 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 scope of a one-way MEP is limited to the exchange of a message between one sending and one receiving SOAP node. Implementations MAY choose to support multiple meps at the same time.
The One-way MEP defines a set of properties described in ???.
| Property Name | Property Description | Property Type |
|---|---|---|
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. | xs:anyURI |
http://www.w3.org/2003/05/soap/mep/ImmediateSender | The identifier of the immediate sender of an inbound message. | xs:anyURI |
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/FailureReason | A value that denotes a pattern-specific, binding-independent reason for the failure of a message exchange. Underlying protocol binding specifications may define properties to convey more binding-specific details of the failure. | xs:anyURI |
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/State | The identifier of the state of the message exchange. This value is managed by the binding instance and may be inspected by other entities monitoring the progress of the message exchange. At a terminal state, it contains either Success or Fail | xs:anyURI |
There may be other properties related to the operation of the message exchange and are processed according to their own feature specifications.