OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Strawman Proposal for New wording of Section 5.2

I have attached, for discussion, a strawman proposal for new wording of 
Section 5.2.

Please provide your comments on this proposal.

Tom Rutt

Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

5.2 Reliability of WSDL Operations

This specification supports Reliable Messaging capabilities for WSDL 1.1 [WSDL 1.1] One-way and Request-response operation types only.

In WSDL 1.1, a one-way operation has a desciption which only has an input message defined.

In WSDL 1.1 a request-response operation has a description which has an input message and an output message defined, and which may also have a fault message defined.

WSDL message descrptions may have one or more message parts defined for an input or an output message.

A WSDL description can be defined to specify the ws-reliability request element as an explicit message part of the operation's input message, along with one or more message parts defining the payload of the reliable message request. The WS-Reliability request element message part would be bound to the Soap Header in a SOAP binding for this operation, when the operation is to be used with WS-Reliability features.

For a request-response WSDL operation, the ws-reliability response element can be defined as an expllicit message part of the operation's output message, along with zero or more output message parts defining the payload of the WSDL operation response. The ws-relibility response element message parts would be bound the the soap Header in a SOAP binding for the operation. Intended to be used with WS-Reliability Features. A WSDL operaton hich has no information bound to the soap Body is still considered a request-response operation, if it has an output message part bound to the soap Header.

In this version of the specifiction, the Respond operation, invoked by the consumer on the receiving RMP, is used to convey to the Receving RMP the abstract message parts which are not bound to the soap header for the WSDL output message soap Binding for a wsdl request-response operation. Its use is out of scope for one-way WSDL operations or for WSDL request response operations which have no output message parts other than those bound to the soap header.

A WSDL description which does not explicitly define ws-reliability request and response elements as message parts for its operations, may be used with WS-reliability. However, in such cases the ws-reliability soap headers are treated as extension elements, and may be ignored by some message receivers. There are also some usage limitations involved when the ws-reliability elements are not defined to be part of the wsdl messages for such a definition, in particular if there is no output message defined for an operation, the respond rm-reply pattern SHOULD NOT be used for BP 1.0 conformance..

While a Request-Reponse operation can use any of the three RM-Reply patterns to receive acknowledgments or faults, a One-way operation (that is one which has no output message parts defined) is restricted (for BP 1.0 conformance) to use either Callback or Poll RM-Reply pattern. Table 26 indicates recommended usage of reply patterns, for two WSDL operaton types. An RMP MUST, at least, support the recommended combinations in Table 26, for the reply patterns and wsdl operation types it supports.

Table 26 WSDL operation types


operation type


RM-Reply pattern


RM-Reply pattern


RM-Reply pattern


WSDL operation type*





WSDL operation type

No **



* The current version of the WS-Reliability protocol does not support reliability of WSDL response messages (the "output" messages in WSDL operations). It only supports reliability of the WSDL request ("input" messages).

** WS-I BP 1.0 disallows sending a SOAP envelope in HTTP response for a one-way WSDL operation. so an RMP is not required to support this. However, this specification does not require an RMP to enforce this restriction (i.e. WS-I BP compliance). The Receiving RMP may determine its behaviour entirely based on message header content, regardless of the WSDL definition.


1) The Response rm-Reply pattern may be used for a wsdl request response operation which only has

  1. While the specification doesn’t prohibit using Callback or Poll RM-Reply patterns to receive acknowledgments or faults for a Request-response operation, it is encouraged to use Response RM-Reply pattern for such operations as the acknowledgment or the fault can be sent on the same message as the WSDL output payoad, thus saving extra round trips.

  2. For this version of the WS-reliability protocol, the used of the Respond operation by the consumer is out of scope for the Callback or Poll RM-Reply patterns.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]