W3C home > Mailing lists > Public > www-ws-desc@w3.org > September 2006

Multiple ports in a WSDL 1.1 service equivalent in WSDL 2

From: Gavan W Hood <gwhood@ra.rockwell.com>
Date: Fri, 1 Sep 2006 18:21:02 +1000
To: www-ws-desc@w3.org
Message-ID: <OF8906DE39.E8832856-ON862571DC.002C55CE-4A2571DC.002DCB2E@ra.rockwell.com>
I would like clarification on a basic feature of WSDL 1.1 to WSDL 2 

In 1.1 there is a neat representation that allows multiple ports (that are 
instances of abstract porttype definitions )to be represented within a 
It appears to me that in  WSDL 2 that port type is now represented as 
I note that  the association of interface to service is 1:1 as interface 
reference is an attribute of the service element.
In 1.1 Ports were elements so you could represent multiple ports with the 
service... which has significant benefit.
For example you may have some operations in a service that are represented 
on a message queue and others that are represented on http connection and 
both are integral parts of the service.

In 1.1 the ports established this relationship quite nicely, in WSDL 2 you 
cannot do this within the spec as far as I can tell. There is talk of 
supporting multiple interfaces and binding operations but neither appears 
to be core functionality and will not be supported. The questions on 
multiple interfaces seem to be related to the problem I think I can see (I 
may be wrong).
As there are WSDL 1.1 to WSDL 2 converters I would assume this issue has 
been resolved and I am just misinterpreting the text.

I naively think that you could get around this by allowing multiple 
bindings of interfaces within a service, something closer to the Port / 
PortType constructs.
I can see this being an area that will receive more attention as SOA 

Can you please explain to me how I will represent this functionality using 
core constructs like I would in WSDL 1.1 please.

Gavan Hood
Received on Friday, 1 September 2006 17:48:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:07:01 UTC