W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > November 2005

2002/ws/desc/wsdl20 wsdl20-adjuncts.xml,1.135,1.136

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 11 Nov 2005 12:27:19 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20051111122719.5FDAA4EED6@homer.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv27434

Modified Files:
	wsdl20-adjuncts.xml 
Log Message:
SOAP MEP / WSDL MEP mapping


Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.135
retrieving revision 1.136
diff -C2 -d -r1.135 -r1.136
*** wsdl20-adjuncts.xml	11 Nov 2005 11:59:58 -0000	1.135
--- wsdl20-adjuncts.xml	11 Nov 2005 12:27:17 -0000	1.136
***************
*** 2634,2661 ****
            the SOAP MEP selected is
            <attval>&soap12-soap-response-mep-uri;</attval>
!           then the IRI to execute the HTTP GET against MUST be
            generated using the HTTP binding extension's rules for generating a
            IRI for HTTP GET (see <specref ref="_http_x-www-form-urlencoded"/>). The
            input serialization format of
!           <code>x-www-form-urlencoded</code> is the only supported
            serialization format for HTTP GET in the SOAP Response
            Message Exchange Pattern.</p>
- 	    <ednote>
- 	      <name>Input serialization for HTTP GET in SOAP HTTP binding</name>
- 	      <edtext>Use of a different input serialization format
- 	      requires introduction of either a new MEP or a new
- 	      binding. The Working Group considered the limitations of
- 	      the <code>x-www-form-urlencoded</code> serialization
- 	      format (see <loc
- 	      href='http://lists.w3.org/Archives/Public/www-ws-desc/2004Jul/0061.html'>points
- 	      #2 and #3 of Binding message content to IRI
- 	      analysis</loc>). It decided that the limitations of the
- 	      serialization format, which could potentially be solved
- 	      by a serialization format extension, were not
- 	      sufficiently broad enough to warrant allowing
- 	      extensibility in input serialization for the
- 	      soap-response MEP. The Working Group solicits the
- 	      public's feedback on this decision.</edtext>
- 	    </ednote>
  	  </item>
          </ulist>
--- 2634,2645 ----
            the SOAP MEP selected is
            <attval>&soap12-soap-response-mep-uri;</attval>
!           then the value of the SOAP
! 	  <attval>&soap12-mep;ImmediateDestination</attval> property MUST be
            generated using the HTTP binding extension's rules for generating a
            IRI for HTTP GET (see <specref ref="_http_x-www-form-urlencoded"/>). The
            input serialization format of
!           <code>application/x-www-form-urlencoded</code> is the only supported
            serialization format for HTTP GET in the SOAP Response
            Message Exchange Pattern.</p>
  	  </item>
          </ulist>
***************
*** 2663,2666 ****
--- 2647,2748 ----
        </div3>
        
+       <div3 id="wsdl-mep-soap-mep">
+ 	<head>Binding WSDL 2.0 MEPs to SOAP 1.2 MEPs</head>
+ 
+ 	<p>This section describes the relationship between WSDL components and SOAP
+ 	1.2 MEP properties as described in <bibref ref="SOAP12-PART2"/>.</p>
+ 
+ 	<div4 id='soap-mep-r-r'>
+ 	  <head>Using SOAP Request-Response</head>
+ 
+ 	  <p>When using the WSDL <attval>&wsdl-mep-in-out;</attval>
+ 	  message exchange pattern bound to a SOAP
+ 	  <attval>&soap12-request-response-mep-uri;</attval>
+ 	  MEP
+ 	  (as would be the case for a usual SOAP-over-HTTP In-Out operation),
+ 	  this section describes the relationships.</p>
+ 
+ 	  <div5>
+ 	    <head>The Client</head>
+ 
+ 	    <p>As the client, the property
+ 	    <attval>&soap12-binding-role;</attval>
+ 	    takes the value <attval>RequestingSOAPNode</attval>.</p>
+ 
+ 	    <p>The SOAP <attval>&soap12-mep;ImmediateDestination</attval>
+ 	    property takes the value of the WSDL <prop
+ 	    comp="Endpoint">address</prop> property of the
+ 	    <comp>Endpoint</comp> component.</p>
+ 
+ 	    <p>The WSDL <attval>In</attval> message is mapped to the SOAP
+ 	    <attval>&soap12-mep;OutboundMessage</attval> property.</p>
+ 
+ 	    <p>The WSDL <attval>Out</attval> message maps to the SOAP
+ 	    <attval>&soap12-mep;InboundMessage</attval> property.</p>
+ 
+ 	  </div5>
+ 
+ 	  <div5>
+ 	    <head>The Service</head>
+ 
+ 	    <p>As the service, the property
+ 	    <attval>&soap12-binding-role;</attval>
+ 	    takes the value <attval>RespondingSOAPNode</attval>.</p>
+ 
+ 	    <p>The WSDL <attval>In</attval> message is mapped to the SOAP
+ 	    <attval>&soap12-mep;InboundMessage</attval> property.</p>
+ 	    
+ 	    <p>The WSDL <attval>Out</attval> message maps to the SOAP
+ 	    <attval>&soap12-mep;OutboundMessage</attval> property.</p>
+ 
+ 	  </div5>
+ 
+ 	</div4>
+ 	<div4>
+ 	  <head>Using SOAP-Response</head>
+ 
+ 	  <p>When using the WSDL <attval>&wsdl-mep-in-out;</attval>
+ 	  message exchange pattern bound to a
+ 	  <attval>&soap12-soap-response-mep-uri;</attval> SOAP MEP,
+ 	  this section describes the relationships.</p>
+ 
+ 	  <div5>
+ 	    <head>The Client</head>
+ 
+ 	    <p>As the client, the property
+ 	    <attval>&soap12-binding-role;</attval>
+ 	    takes the value <attval>RequestingSOAPNode</attval>.</p>
+ 
+ 	    <p>The SOAP <attval>&soap12-mep;ImmediateDestination</attval>
+ 	    property takes the value of the WSDL <prop
+ 	    comp="Endpoint">address</prop> property, modified
+ 	    by the <prop comp="Binding Operation">http location</prop>
+ 	    property following the rules described in section <specref ref="_http_x-www-form-urlencoded"/>.</p>
+ 
+ 	    <p>The SOAP <attval>&soap12-mep;OutboundMessage</attval> property
+ 	    has no value.</p>
+ 
+ 	    <p>The WSDL <attval>Out</attval> message maps to the SOAP
+ 	    <attval>&soap12-mep;InboundMessage</attval> property.</p>
+ 
+ 	  </div5>
+ 
+ 	  <div5>
+ 	    <head>The Service</head>
+ 
+ 	    <p>As the service, the property
+ 	    <attval>&soap12-binding-role;</attval>
+ 	    takes the value <attval>RespondingSOAPNode</attval>.</p>
+ 
+ 	    <p>The WSDL <attval>In</attval> message is constructed from the destination URI as per the
+ 	    rules in section <specref ref="_http_x-www-form-urlencoded"/>.</p>
+ 
+ 	    <p>The WSDL <attval>Out</attval> message maps to the SOAP
+ 	    <attval>&soap12-mep;OutboundMessage</attval> property.</p>
+ 
+ 	  </div5>
+ 	</div4>
+       </div3>
+ 
        </div2>
        
***************
*** 5252,5255 ****
--- 5334,5346 ----
  	      <td>20051111</td>
  	      <td>HH</td>
+ 	      <td>Added SOAP MEP / WSDL MEP mapping as per
+ 	      <loc
+ 	      href='http://lists.w3.org/Archives/Public/www-ws-desc/2005Nov/0022.html'>resolution</loc>
+ 	      </td>
+ 	    </tr>
+ 
+ 	    <tr>
+ 	      <td>20051111</td>
+ 	      <td>HH</td>
  	      <td><loc
  	      href="http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC333">LC333</loc>:
Received on Friday, 11 November 2005 12:27:22 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Friday, 11 November 2005 12:27:22 GMT