index.html
17.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>SOAP 1.2 Part 3: One-Way MEP</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE.css"></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p>
<h1><a name="title" id="title"></a>SOAP 1.2 Part 3: One-Way MEP</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Group Note 2 July 2007</h2><dl><dt>This version:</dt><dd>
<a href="http://www.w3.org/TR/2007/NOTE-soap12-part3-20070702/">http://www.w3.org/TR/2007/NOTE-soap12-part3-20070702/</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/soap12-part3/">http://www.w3.org/TR/soap12-part3/</a>
</dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2006/WD-soap12-part3-20061219/">http://www.w3.org/TR/2006/WD-soap12-part3-20061219/</a>
</dd><dt>Editor:</dt><dd>David Orchard, BEA Systems</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2007 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.</p></div><div>
<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p><p>This document is a <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#q75">Working Group Note</a> of the W3C. It has been produced by the <a href="http://www.w3.org/2000/xp/Group/">XML Protocol Working Group</a>, which
is part of the <a href="http://www.w3.org/2002/ws/Activity">Web Services
Activity</a>.</p><p>As of the publication of this Working Group Note the <a href="http://www.w3.org/2000/xp/Group/">XML Protocol Working Group</a> has completed work on this document. Major changes to this specification can be found in the <a href="#changelog">Changelog</a>. Please report errors in this document to the public mailing list <a href="mailto:xmlp-comments@w3.org">xmlp-comments@w3.org</a>
(<a href="http://lists.w3.org/Archives/Public/xmlp-comments/">archive</a>).
It is inappropriate to send discussion email to this address.</p><p>Publication as a Working Group Note does not imply endorsement
by the W3C Membership. This is a draft document and may be updated, replaced or
obsoleted by other documents at any time. It is inappropriate to cite this
document as other than work in progress.</p><p> This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/32157/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p><p>A list of current <a href="http://www.w3.org/TR/">W3C Recommendations and
other technical reports</a> can be found at <a href="http://www.w3.org/TR">http://www.w3.org/TR</a>.</p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br>
1.1 <a href="#notcon">Notational Conventions</a><br>
2 <a href="#singlereqmep">SOAP One-way Message Exchange Pattern</a><br>
2.1 <a href="#mepname">SOAP Feature Name</a><br>
2.2 <a href="#bindinfdesc">Description</a><br>
2.3 <a href="#bindformdesc">Property Description</a><br>
2.4 <a href="#bindfaulthdn">Fault Handling</a><br>
3 <a href="#refs">References</a><br>
3.1 <a href="#refs-norm">Normative References</a><br>
3.2 <a href="#refs-inform">Informative References</a><br>
</p>
<h3><a name="appendices" id="appendices"></a>Appendix</h3><p class="toc">A <a href="#changelog">Change Log</a> (Non-Normative)<br>
</p></div><hr><div class="body"><div class="div1">
<h2><a name="intro" id="intro"></a>1 Introduction</h2><p>SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.
</p><div class="div2">
<h3><a name="notcon" id="notcon"></a>1.1 Notational Conventions</h3><p>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 <a href="#RFC2119">[RFC 2119]</a>.</p><p>With the exception of examples and sections explicitly marked
as "Non-Normative", all parts of this specification are
normative.</p></div></div><div class="div1">
<h2><a name="singlereqmep" id="singlereqmep"></a>2 SOAP One-way Message Exchange Pattern</h2><p>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.</p><div class="div2">
<h3><a name="mepname" id="mepname"></a>2.1 SOAP Feature Name</h3><p>This message exchange pattern is identified by
the URI (see SOAP 1.2 Part 1 <a href="#SOAP-PART1">[SOAP Part 1]</a>
<a href="http://www.w3.org/TR/2007/REC-soap12-part1-20070427//#soapfeature">SOAP Features</a>):</p><ul><li><p>
"http://www.w3.org/2006/08/soap/mep/one-way/"
</p></li></ul></div><div class="div2">
<h3><a name="bindinfdesc" id="bindinfdesc"></a>2.2 Description</h3><p>The SOAP One-way MEP defines
properties for the exchange of a SOAP message. In the absence of failure in the underlying protocol,
this MEP consists of zero or more SOAP messages. The scope of a one-way MEP instance is limited to transmission of messages from one sending node to zero or more receiving SOAP node(s). The ImmediateSender and ImmediateDestination properties may differ among nodes. The envelope in the InboundMessage property at each successful receiver SHOULD be identical to the envelope in the OutboundMessage at the sender. Implementations MAY choose
to support multiple MEPs at the same time.</p><p>The sending node MUST attempt to send, in a binding-specific manner, the SOAP Message provided in http://www.w3.org/2003/05/soap/mep/OutboundMessage to the node(s) identified by http://www.w3.org/2003/05/soap/mep/ImmediateDestination. If the sender has a means of detecting successful or unsuccessful transmission, it SHOULD fault in a binding-specific manner in the event that transmission failure is detected.</p><p>When a message is successfully received by a SOAP node, that node MUST populate http://www.w3.org/2003/05/soap/mep/InboundMessage with the received message and MUST process the message in http://www.w3.org/2003/05/soap/mep/InboundMessage according to the SOAP Processing Model (see SOAP 1.2 Part 1 <a href="#SOAP-PART1">[SOAP Part 1]</a><a href="http://www.w3.org/TR/2007/REC-soap12-part1-20070427//#procsoapmsgs">Processing SOAP messages</a>). A receiver MAY (though typically only in exceptional circumstances) treat as erroneous, or lost, a message that has been received intact. Typical reasons for making such decisions might include shortage of buffer space, network interface overruns, etc.. A receiver MAY fault in a binding-specific manner if some particular message is determined to have been unsuccessfully received (note, however, that in many cases where receipt is unsuccessful, information identifying the message or its sender may be unreliable, in which case there may be little if any value in reflecting a message-specific fault.)</p></div><div class="div2">
<h3><a name="bindformdesc" id="bindformdesc"></a>2.3 Property Description</h3><p>The One-way MEP defines a set of properties described below.</p><a name="tabonewayprops" id="tabonewayprops"></a><table border="1"><caption>Property definitions for One-way MEP</caption><tbody><tr><th>Property Name</th><th>Property Description</th><th>Property Type</th></tr><tr><td>
<code>http://www.w3.org/2003/05/soap/mep/InboundMessage</code>
</td><td>An 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. This property is populated if and only if the message is successfully received.</td><td>Not specified</td></tr><tr><td>
<code>http://www.w3.org/2003/05/soap/mep/OutboundMessage</code>
</td><td>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.</td><td>Not specified</td></tr><tr><td>
<code>http://www.w3.org/2003/05/soap/mep/ImmediateDestination</code>
</td><td>The identifier of the immediate destination of an
outbound message. (NOTE: the URI supplied MAY be the identifier of a single destination SOAP node, or MAY be the identifier of a multicast group, which itself consists
of zero or more destination nodes. Whether multicast is supported is
binding-dependent. This MEP specification provides no standard means for representing a multicast group, except to require that the group as a whole be designated by a URI.)</td><td>xs:anyURI</td></tr><tr><td>
<code>http://www.w3.org/2003/05/soap/mep/ImmediateSender</code>
</td><td>The identifier of the immediate sender of an inbound
message.</td><td>xs:anyURI</td></tr></tbody></table><p>This MEP MAY be extended by later
specifications. Such extensions MAY add additional properties to the ones
listed above. </p></div><div class="div2">
<h3><a name="bindfaulthdn" id="bindfaulthdn"></a>2.4 Fault Handling</h3><p>Each SOAP node involved in the message exchange makes its own
determination of successful completion of the message exchange. Each
node MAY independently signal a fault in the case of abnormal
operation. Determination of successful operation and disposition of
faults are outside the scope of this specification.</p></div></div><div class="div1">
<h2><a name="refs" id="refs"></a>3 References</h2><div class="div2">
<h3><a name="refs-norm" id="refs-norm"></a>3.1 Normative References</h3><dl><dt class="label"><a name="SOAP-PART1" id="SOAP-PART1"></a>SOAP Part 1</dt><dd>
<a href="http://www.w3.org/TR/2007/REC-soap12-part1-20070427/"><cite>SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)</cite></a>,
Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau,
Henrik Frystyk Nielsen, Anish Karmarkar, Yves Lafon, Editors.
World Wide Web Consortium, 27 April 2007.
This version is http://www.w3.org/TR/2007/REC-soap12-part1-20070427/.
The <a href="http://www.w3.org/TR/soap12-part1/">latest version</a> is
available at http://www.w3.org/TR/soap12-part1/.</dd><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC 2119</dt><dd>
<a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for
use in RFCs to Indicate Requirement Levels</cite></a>, S. Bradner,
Editor.
IETF, March 1997.
This RFC is available at http://www.ietf.org/rfc/rfc2119.txt.</dd><dt class="label"><a name="RFC3986" id="RFC3986"></a>RFC 3986</dt><dd>
<a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource
Identifiers (URI): Generic Syntax</cite></a>, T. Berners-Lee,
R. Fielding and L. Masinter, Editors.
IETF, January 2005.
<em>Obsoletes: <span id="RFC2396">RFC 2396</span>,
<span id="RFC2732">RFC 2732</span></em>.
This RFC is available at http://www.ietf.org/rfc/rfc3986.txt.</dd></dl></div><div class="div2">
<h3><a name="refs-inform" id="refs-inform"></a>3.2 Informative References</h3><dl><dt class="label"><a name="SOAP-PART0" id="SOAP-PART0"></a>SOAP Part 0</dt><dd>
<a href="http://www.w3.org/TR/2007/REC-soap12-part0-20070427/"><cite>SOAP Version 1.2 Part 0: Primer (Second Edition)</cite></a>,
Nilo Mitra, Yves Lafon, Editors.
World Wide Web Consortium, 27 April 2007.
This version is http://www.w3.org/TR/2007/REC-soap12-part0-20070427/.
The <a href="http://www.w3.org/TR/soap12-part0/">latest version</a> is
available at http://www.w3.org/TR/soap12-part0/.</dd><dt class="label"><a name="SOAP-PART2" id="SOAP-PART2"></a>SOAP Part 2</dt><dd>
<a href="http://www.w3.org/TR/2007/REC-soap12-part2-20070427/"><cite>SOAP Version 1.2 Part 2: Adjuncts (Second Edition)</cite></a>,
Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau,
Henrik Frystyk Nielsen, Anish Karmarkar, Yves Lafon, Editors.
World Wide Web Consortium, 27 April 2007.
This version is http://www.w3.org/TR/2007/REC-soap12-part2-20070427/.
The <a href="http://www.w3.org/TR/soap12-part2/">latest version</a> is
available at http://www.w3.org/TR/soap12-part2/.</dd><dt class="label"><a name="CommentArchive" id="CommentArchive"></a>XMLP Comments</dt><dd>XML Protocol Comments Archive (See http://lists.w3.org/Archives/Public/xmlp-comments/.)</dd><dt class="label"><a name="DiscussionArchive" id="DiscussionArchive"></a>XMLP Dist-App</dt><dd>XML Protocol Discussion
Archive (See http://lists.w3.org/Archives/Public/xml-dist-app/.)</dd><dt class="label"><a name="XMLPCharter" id="XMLPCharter"></a>XMLP Charter</dt><dd>XML Protocol Charter (See http://www.w3.org/2000/09/XML-Protocol-Charter.)</dd><dt class="label"><a name="RFC2045" id="RFC2045"></a>RFC 2045</dt><dd>IETF "RFC2045: Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", N. Freed, N. Borenstein, November 1996. (See http://www.ietf.org/rfc/rfc2045.txt.)</dd><dt class="label"><a name="RFC2026" id="RFC2026"></a>RFC 2026</dt><dd>IETF "RFC 2026:
The Internet Standards Process -- Revision 3", section
4.2.3, S. Bradner, October 1996. (See http://www.ietf.org/rfc/rfc2026.txt.)</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="changelog" id="changelog"></a>A Change Log (Non-Normative)</h2><table border="1"><caption>Changes</caption><thead><tr><th>Who</th><th>When</th><th>What</th></tr></thead><tbody><tr><td>DBO</td><td>20041208</td><td>Initial Revision</td></tr><tr><td>DBO</td><td>20060330</td><td>2nd Revision</td></tr><tr><td>DBO</td><td>20060530</td><td>Adding sending and receiver MUSTs</td></tr><tr><td>DBO</td><td>20060720</td><td>Update date parts, checked into cvs, and moved abnormal operation paragraph to end of 2.2</td></tr><tr><td>DBO</td><td>20060803</td><td>Added InboundMessage property and text about populating, removed State property, other minor edits. Moved to xmlspec 2.10 dtd and xmlspec.xsl 1.54 (2005/10/13) </td></tr><tr><td>DBO</td><td>20060809</td><td>Removed failureReason property, explicit support for multicast by saying 0 or more nodes, changing "the receiver" to "a receiver" etc. </td></tr><tr><td>DBO</td><td>20060830</td><td>Some more clarifications on multicast, added ednote for feedback.</td></tr><tr><td>DBO</td><td>20070330</td><td>Did Mutiple fixes based on WSDL WG comments. Minutes at http://www.w3.org/2007/03/21-xmlprotocol-minutes.html, WSDL Comments at http://lists.w3.org/Archives/Public/xmlp-comments/2007Feb/0000.html. WG made decisions about 1, 5, 10, 11. Items 2,3 done at editors discretion. </td></tr><tr><td>DBO</td><td>20070425</td><td>Did 2 fixes, http://www.w3.org/Bugs/Public/show_bug.cgi?id=4404, http://www.w3.org/Bugs/Public/show_bug.cgi?id=4407. Minutes at http://www.w3.org/2007/04/25-xmlprotocol-minutes.html. Also removed Ed note.</td></tr><tr><td>DBO</td><td>20070516</td><td>Did 2 fixes, first 2 of Noah's comments from 5/4/2007 and moved error handling out of 2.2</td></tr></tbody></table></div></div></body></html>