- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 04 May 2005 09:58:05 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv27708
Modified Files:
wsdl20.xml
Log Message:
Rewrote the "Single Interface" section, as per editorial AI dated 2005-01-19.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.250
retrieving revision 1.251
diff -C2 -d -r1.250 -r1.251
*** wsdl20.xml 3 May 2005 16:31:09 -0000 1.250
--- wsdl20.xml 4 May 2005 09:58:03 -0000 1.251
***************
*** 9391,9402 ****
<head>Single Interface per Service</head>
<p>
! WSDL 1.1 imposed no restriction on the portTypes implemented by the ports within a service.
! WSDL 2.0 requires that within a service,
! all endpoints (previously called ports) implement the same interface (previously called portType).
! Therefore, when migrating a service from WSDL 1.1 to WSDL 2.0 any service that implemented more than one portType
! must be mapped to one or more services, each of which implementing a single interface.
! To indicate that these new services are related to each other, they can be placed
! in the same document, or in one or more documents with the same targetNamespace.
</p>
</div2>
--- 9391,9438 ----
<head>Single Interface per Service</head>
<p>
! WSDL 2.0 requires that within a service, all endpoints (called ports in WSDL 1.1)
! implement exactly the same interface (called portType in WSDL 1.1).
! WSDL 1.1 imposed no such restriction. WSDL 1.1 documents could contain ports, from the same service,
! that implemented differents portTypes. Such WSDL 1.1 documents must therefore be converted, before
! they are valid WSDL 2.0 documents. Note: other types of conversions may also be required,
! because of other differences between WSDL 2.0 and WSDL 1.1. These differences are not considered
! further in this section.
</p>
+ <p>
+ To convert a WSDL 1.1 document that contains ports from the same service that implement different
+ portTypes, one must first move each portType implementing a different port to a new service. The new service
+ is a replica of the original service, apart from the fact that it implements a different set of portTypes.
+ </p>
+ <p>
+ Is is then generally desirable to indicate that the new services are related to each other.
+ This can be achieved by using one of the following alternatives:
+ </p>
+ <olist>
+ <item><p>
+ <b>Single document</b>.
+ Keep the new services under the same <el>definition</el> &EII;.
+ </p></item>
+
+ <item><p>
+ <b>Multiple documents, same targetNamespace</b>.
+ Split the new services over multiple WSDL 2.0 documents,
+ each with the same <att>targetNamespace</att>.
+ </p></item>
+
+ <item><p>
+ <b>Multiple documents, same endpoint</b>.
+ Split the new services in multiple WSDL 2.0 documents,
+ each with the same <el>endpoint</el>. Note that this provides
+ a looser coupling that the <att>targetNamespace</att> alternative above.
+ </p></item>
+
+ <item><p>
+ <b>Extension</b>.
+ Use a WSDL 2.0 extension whose semantics would be to link the new services
+ together. This is somewhat analoguous to the <att>targetNamespace</att> approach above,
+ although such an extension may carry additional semantics.
+ The definition of such an extension is outside the scope of this specification.
+ </p></item>
+ </olist>
</div2>
***************
*** 9622,9625 ****
--- 9658,9667 ----
<tr>
+ <td>20050504</td>
+ <td>JJM</td>
+ <td>Rewrote the "Single Interface" section, as per editorial AI dated 2005-01-19.</td>
+ </tr>
+
+ <tr>
<td>20050503</td>
<td>JJM</td>
Received on Wednesday, 4 May 2005 09:58:09 UTC