1.1 Notational Conventions
2 SOAP One-way Message Exchange Pattern
2.1 SOAP Feature Name
2.3 Property Description
2.4 Fault Handling
3.1 Normative References
3.2 Informative References
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.
Bindings MAY define more detailed behavior in the case of abnormal operation. Bindings MAY choose to support multiple instances of this MEP simultaneously.
|Property Name||Property Description||Property Type|
||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|
||The identifier of the immediate destination of an outbound message.||xs:anyURI|
||The identifier of the immediate sender of an inbound message.||xs:anyURI|
|DBO||20060530||Adding sending and receiver MUSTs|