This document describes Web Services Description Language (WSDL) Version 1.2 message patterns. These patterns are intended for use with the Web Services Description Language (WSDL).
This is the first
This document has been produced as part of the
This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or members of the Web Services Description Working Group.
Comments on this document are invited and are to be sent to
Patent disclosures relevant to this specification may be found on
the Working Group's
A list of
Last Modified: $Date: 2003/06/10 12:19:06 $
Web Services Description Language (WSDL) message patterns define the sequence, direction, and cardinality of abstract messages sent or received by an operation.
By design, WSDL message patterns abstract out specific message types; placeholders for messages identified by the pattern are associated with specific message types by the operation using the pattern.
Unless explicitly stated otherwise, WSDL message patterns also abstract out binding-specific information like timing between messages, whether the pattern is synchronous or asynchronous, and whether the message are sent over a single or multiple channels.
This specification defines several message patterns for
use with
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119
WSDL patterns are described in terms of the WSDL component model, specifically the message reference and fault reference components.
This pattern consists of exactly one message as follows:
A message indicated by a message reference whose {name} is 'A' and {direction} is 'in'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/in-only'.
This pattern consists of exactly two messages, in order, as follows:
A message indicated by a message reference whose {name} is 'A' and {direction} is 'in'.
One of the following:
A message indicated by a message reference whose {name} is 'B' and {direction} is 'out', or
A message indicated by a fault reference whose {name} is 'C' and {direction} is 'out'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/in-out'.
This pattern is identical to
Any message with {direction} 'out' is sent on the same channel as the message with {direction} 'in'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/request-response'.
This pattern consists of one or more messages, in order, as follows:
A message indicated by a message reference whose {name} is 'A' and {direction} is 'in'.
Zero or more messages indicated by a message reference whose {name} is 'B' and {direction} is 'out'.
An optional message indicated by a fault reference whose {name} is 'C' and {direction} is 'out'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/in-multi-out'.
This pattern consists of exactly one message as follows:
A message indicated by a message reference whose {name} is 'A' and {direction} is 'out'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/out-only'.
This pattern consists of exactly two messages, in order, as follows:
A message indicated by a message reference whose {name} is 'A' and {direction} is 'out'.
One of the following:
A message indicated by a message reference whose {name} is 'B' and {direction} is 'in', or
A message indicated by a fault reference whose {name} is 'C' and {direction} is 'in'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/out-in'.
This pattern consists of one or more messages, in order, as follows:
A message indicated by a message reference whose {name} is 'A' and {direction} is 'out'.
Zero or more messages indicated by a message reference whose {name} is 'B' and {direction} is 'in'.
An optional message indicated by a fault reference whose {name} is 'C' and {direction} is 'in'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/out-multi-in'.
This pattern consists of one or more messages, in sequence as follows:
A message indicated by a message reference whose {name} is 'A' and {direction} is 'out',
Zero or more messages, each of which is in one of the following sequences:
One or two messages, in sequence as follows:
A message indicated by a message reference whose {name} is 'B' and {direction} is 'in',
A message indicated by a fault reference whose {name} is 'D' and {direction} is 'out'.
A message indicated by a fault reference whose {name} is 'C' and {direction} is 'in'.
An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/multicast-solicit-response'.
This document is the work of the W3C Web Service Description Working Group.
Members of the Working Group are (at the time of writing, and by
alphabetical order): Adi Sakala (IONA Technologies),
Alan Davies (SeeBeyond),
Allen Brookes (Rogue Wave Softwave),
Amelia Lewis (TIBCO/Extensibility),
Arthur Ryman (IBM),
Bijan Parsia (University of Maryland),
Dale Moberg (Cyclone Commerce),
Dan Kulp (IONA Technologies),
David Booth (W3C),
Dietmar Gaertner (Software AG),
Don Mullen (TIBCO Software),
Erik Ackerman (Lexmark),
Glen Daniels (Macromedia),
Igor Sedukhin (Computer Associates),
Ingo Melzer (DaimlerChrysler Research and Technology),
Jacek Kopecky (Systinet),
Jean-Jacques Moreau (Canon),
Jeff Mischkinsky (Oracle Corporation),
Jeffrey Schlimmer (Microsoft Corporation),
Jerry Thrasher (Lexmark),
Jim Hendler (University of Maryland),
Johan Pauhlsson (L'Échangeur),
Jonathan Marsh (
Previous members were: Aaron Skonnard (DevelopMentor), Don Wright (Lexmark), Barbara Zengler (DaimlerChrysler Research and Technology), Jochen Ruetschlin (DaimlerChrysler Research and Technology), Joyce Yang (Oracle Corporation), Keith Ballinger (Microsoft), Krishna Sankar (Cisco Systems), Mario Jeckle (DaimlerChrysler Research and Technology), Pallavi Malu (Intel Corporation), William Stumbo (Xerox), Daniel Schutzer (Citigroup), Dave Solo (Citigroup), Stefano Pogliani (Sun Microsystems), Stephen White (SeeBeyond), Tim Finin (University of Maryland)
The people who have contributed to discussions on
| Date | Author | Description |
|---|---|---|
| 20030313 | MJG | Changed to Part 2 ( from Part 3 ) |
| 20030306 | JCS | Proposed name for MEP7. |
| 20030305 | JCS | Per 4 Mar 03 meeting, renamed 'message exchange pattern' to 'message pattern' or 'pattern', added pattern for request-response, added ednote about review of patterns. |
| 20030217 | MJG | Fixed some issues with entities and validity errors WRT ulists |
| 20030212 | JCS | Initial draft |