W3C home > Mailing lists > Public > www-ws-desc@w3.org > October 2002

Re: Updated portTypeExtension proposal

From: Peter Vanderbilt <pv@nas.nasa.gov>
Date: Wed, 09 Oct 2002 15:56:49 -0700
Message-ID: <3DA4B431.E960F8FE@nas.nasa.gov>
To: www-ws-desc@w3.org

What's the current thinking about the following questions related to
portType inheritance:

Assume portType C derives from portTypes A and B.  What appears as
wsdl:port elements in wsdl:service?  Is there one port element or
three?

If one, is its binding structured in a way that allows independent
binding mechanisms for A and B?  Different addresses?  Can a client
that operates on services containing (wsdl:) port A (and doesn't know
about C) operate on a service containing port C?  In other words, is
each C port also an A port?

If the example above results in three ports, how are the operations
allocated to the ports?  Presumably there are ports for A and B
separately.  Does the port for C reference operation bindings for just
those directly defined in portType C?  Or does it include operation
bindings for A and B?  Is it legal for a service to have a C port
without both A and B ports?

Pete

P.S.  I'm a member of the Global Grid Forum OGSI group but not an
official representative.  (The ignorance is my own.)


Martin Gudgin wrote:
> 
> An updated version of the port type extension proposal is at[1]. The
> only major change is to the mapping of the {port type] property on the
> service component[2] to allow multiple port types.
> 
> Gudge
> 
> [1]
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.ptext.ser
> vice.ptmult.html
> [2]
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.ptext.ser
> vice.ptmult.html#Service_Mapping
Received on Wednesday, 9 October 2002 19:00:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:21 GMT