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

Port Type Inheritance

From: Ricky Ho <riho@cisco.com>
Date: Fri, 06 Sep 2002 22:33:01 -0700
Message-Id: <4.3.2.7.2.20020906222011.027931d0@franklin.cisco.com>
To: www-ws-desc@w3.org

Hi,

Do we have any discussion around whether we need to provide inheritance for 
WSDL PortType.  By inheritance, I mean the same concept as the Java 
interface inheritance.  I do see two use cases.

1) Administrative operation
====================
For enterprise scale deployment, I want to monitor the health status of all 
my web services, as well as to remote turn on debugging.  Therefore, I want 
to mandate all my services to support certain operations such as "reset", 
"getHealthStatus".  However, I have no way to enforce that at this moment.
It would be nice if I just need to tell my developer that their PortType 
need to inherit "ManagablePortType" where such operations are defined.

2) Change control
=============
WSDL itself will evolve and change, but how do we make sure the newer 
version is backward compatible to the old one so existing client won't 
break.  If we have PortType inheritance, then the new PortType just need to 
inherit the old PortType.  Of course, the implementation can optionally 
throw a SOAP fault so that the client will be upgraded.

Thoughts and comments ??

Best regards,
Ricky
Received on Saturday, 7 September 2002 01:33:33 GMT

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