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.
2.2 Description
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 might, 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.)
Each SOAP node involved in the message exchange makes its own determination of the successful completion of the message exchange. Each node MAY independently signal a fault in the case of abnormal operation. Determination of abnormal operation is outside the scope of this specification. Disposition of such faults is outside the scope of this MEP.
2.3 Property Description
The One-way MEP defines a set of properties described below.
Property definitions for One-way MEP| 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.
2.4 Fault Handling
During the operation of the One-way MEP, the
participating SOAP nodes may generate SOAP faults. This MEP makes no claims about the disposition or
handling of SOAP faults generated by the sending SOAP node or the receiving SOAP node.