W3C home > Mailing lists > Public > www-ws-desc@w3.org > December 2004

{soap mep} property and SOAP 1.1 Binding

From: Asir Vedamuthu <asirv@webmethods.com>
Date: Wed, 15 Dec 2004 06:34:46 -0800
Message-ID: <5B10E50E14A4594EB1B5566B69AD9407068E6931@maileast>
To: www-ws-desc@w3.org

Background Info

"{soap mep}, a wsdls:anyURI, which is an absolute URI as defined by [IETF
RFC 2396], to the Binding Operation component. The value of this property
identifies the SOAP Message Exchange Pattern (MEP) for this specific
operation. If no specific value is assigned, then the value assigned by the
default rules apply (for SOAP 1.2, see 2.10.3 Default Binding Rules). It is
an error for this property to not have a value (which MAY happen if the
default rules are not applicable)." - Part 3

Last sentence, it is an error if {soap mep} property does not have a value.
As I recall, this is the reason why I made up those spooky URIs for SOAP 1.1
Binding. At the last face to face, we decided to drop those URIs, ignore
{soap mep} property, and rely on Interface Operation component's {message
exchange pattern} property.


For SOAP 1.1 binding, {soap mep} property has no value. Per Part 3, it is an
error if {soap mep} property does not have a value.

Proposed Solution

In Part 3, move this constraint from Binding Operations to SOAP 1.2 Binding

Asir S Vedamuthu
asirv at webmethods dot com
Received on Wednesday, 15 December 2004 14:34:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:51 UTC