SOAP One-way MEP

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

This version:
/
Editor:
David Orchard, BEA Systems

Abstract

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.

Status of this Document

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.

Table of Contents

1 Introduction
1.1 Notational Conventions
2 SOAP One-way Message Exchange Pattern
2.1 SOAP Feature Name
2.2 Description
2.3 State Machine Description
2.4 Fault Handling
3 References
3.1 Normative References
3.2 Informative References

Appendix

A Change Log (Non-Normative)


1 Introduction

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.

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.3 State Machine Description

The One-way MEP defines a set of properties described in ???.

Property definitions for One-way MEP
Property NameProperty DescriptionProperty Type
http://www.w3.org/2003/05/soap/mep/OutboundMessageAn 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/InboundMessageAn 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.Not specified
http://www.w3.org/2003/05/soap/mep/ImmediateDestinationThe identifier of the immediate destination of an outbound message.xs:anyURI
http://www.w3.org/2003/05/soap/mep/ImmediateSenderThe identifier of the immediate sender of an inbound message.xs:anyURI

To initiate a message exchange conforming to the One-way MEP, the sending SOAP node instantiates a local message exchange context. ??? describes how the context is initialized.

Instantiation of a Message Exchange Context for a sending SOAP node
Property NameProperty ValueNotes
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/ExchangePatternName"http://www.w3.org/2006/03/soap/mep/one-way/"
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/FailureReason"None" A relative URI whose base URI is the value of http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/ExchangePatternName
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/Role"SendingSOAPNode" A relative URI whose base URI is the value of http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/ExchangePatternName
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/State"Init" A relative URI whose base URI is the value of http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/Role
http://www.w3.org/2003/05/soap/mep/OutboundMessageAn abstraction of the One-way message
http://www.w3.org/2003/05/soap/mep/ImmediateDestinationAn identifier (URI) that denotes the receiving SOAP node

There may be other properties related to the operation of the message exchange context instance. Such properties are initialized according to their own feature specifications.

Once the message exchange context is initialized, control of the context is passed to a (conforming) local binding instance.

The diagram below shows the logical state transitions at the sending and receiving SOAP nodes during the lifetime of the message exchange. At each SOAP node, the local binding instance updates (logically) the value of the http://www.w3.org/2003/05/soap/bindingFramework/ ExchangeContext/State property to reflect the current state of the message exchange. The state names are relative URIs, relative to a base URI value carried in the http://www.w3.org/2003/05/soap/bindingFramework/ ExchangeContext/Role property of the local message exchange context.

Example: One-way MEP State Transition Diagram
One-way MEP State Transition Diagram.

When the local binding instance at the receiving SOAP node starts to receive an inbound One-way message, it (logically) instantiates a message exchange context. ??? describes the properties that the binding initializes as part of the context's instantiation.

Instantiation of Message Exchange Context for an inbound One-way message at a receiving SOAP node
Property NameProperty ValueNotes
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/ExchangePatternName"http://www.w3.org/2006/03/soap/mep/one-way/"Initialized as early as possible during the life cycle of the message exchange.
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/FailureReason"None"A relative URI whose base URI is the value of http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/ExchangePatternName
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/Role"ReceivingSOAPNode" A relative URI whose base URI is the value of http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/ExchangePatternName Initialized as early as possible during the life cycle of the message exchange.
http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/State"Init"A relative URI whose base URI is the value of http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/Role

When the sending and receiving SOAP nodes transition between states, the local binding instance (logically) updates a number of properties. ??? and ??? describe these updates for the sending and the receiving SOAP nodes, respectively.

Sending SOAP Node State Transitions
CurrentStateTransition ConditionNextStateAction
"Init"Unconditional"Sending"Initiate transmission of message abstracted in http://www.w3.org/2003/05/soap/mep/OutboundMessage.
"Sending"Message transmission failure"Fail"Set http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/FailureReason to "transmissionFailure"
Completed sending message. "Success"

Receiving SOAP Node State Transitions
CurrentStateTransition ConditionNextStateAction
"Init"Start receiving message"Receiving"Set http://www.w3.org/2003/05/soap/mep/ImmediateSender to denote the sender of the message (if determinable). Start making an abstraction of the message available in http://www.w3.org/2003/05/soap/mep/InboundMessage. Pass control of message exchange context to SOAP processor.
"Receiving"Message reception failure"Fail"Set http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/FailureReason to "receptionFailure".
Completed receiving message."Success"

3 References

A Change Log (Non-Normative)

Changes since candidate recommendation.
WhoWhenWhat
DBO20041208Initial Revision
DBO200603302nd Revision