SOAP 1.2 Part 3: One-Way MEP

2 SOAP One-way Message Exchange Pattern

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.1 SOAP Feature Name

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/"

2.2 Description

The SOAP One-way MEP defines properties for the exchange of a SOAP message.

In an instance of this MEP, a single sending SOAP node establishes a message consisting of a set of properties as defined below and sends it in a binding-specific way. A binding MUST define

A mechanism for sending nodes to send a message.
A mapping from the ImmediateDestination property of the message to zero or more receiving SOAP nodes. This mapping MAY vary from instance to instance of the MEP.
A mechanism for receiving nodes to be notified of receipt of a message.

In normal operation

Each receiving node is notified of receipt of the sent message exactly once.
The properties of each received message are identical to the properties of the sent message.
Each receiving node processes the received message according to the SOAP Processing Model (see SOAP 1.2 Part 1 [SOAP Part 1]Processing SOAP messages).

In abnormal operation, any of the following may happen:

Nodes in the receiving set MAY fail to be notified of message receipt or may be notified more than once.
Nodes in the receiving set MAY receive messages not identical to the sent message.
Nodes not in the receiving set MAY be notified of message receipt, regardless of whether nodes in the receiving set have been notified of receipt.
The sending node and/or any of the reciving nodes MAY receive a fault, regardless of whether nodes in the receiving net have been notified of receipt.

Bindings MAY define more detailed behavior in the case of abnormal operation. Bindings MAY choose to support multiple instances of this MEP simultaneously.

2.3 Property Description

The One-way MEP defines the properties described below.

Property definitions for One-way MEP
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

There may be other properties related to the operation of the message exchange and are processed according to their own feature specifications.

2.4 Fault Handling

This MEP makes no claims about the disposition or handling of SOAP faults generated by the sending SOAP node or the receiving SOAP nodes.

A Change Log (Non-Normative)

Changes
Who	When	What
DBO	20041208	Initial Revision
DBO	20060330	2nd Revision
DBO	20060530	Adding sending and receiver MUSTs
DMH	20060616	Clarified semantics.

Changes

Who

When

What

DBO

20041208

Initial Revision

DBO

20060330

2nd Revision

DBO

20060530

Adding sending and receiver MUSTs

DMH

20060616

Clarified semantics.

SOAP 1.2 Part 3: One-Way MEP

Editors Copy $Date: 2006/03/30 09:53:43 $ 16 June 2006

Abstract

Status of this Document

Table of Contents

Appendix

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)