W3C home > Mailing lists > Public > www-ws-desc@w3.org > April 2003

Inheritance and parameter overloading in WSDL1.2

From: Ricky Ho <riho@cisco.com>
Date: Wed, 02 Apr 2003 10:50:49 -0800
Message-Id: <4.3.2.7.2.20030402094638.029c8c28@franklin.cisco.com>
To: www-ws-desc@w3.org

I have some questions regarding the "inheritance" of Port types, Message 
types ... etc.

Here are the message types
=====================

ComplexType Address {
         String street;
         String city;
}

ComplexType USAddress extends Address {
         String state;
         String zip;
}

ComplexType UKAddress extends Address {
         String postCode;
}

ComplexType PurchaseOrder {
         String poNumber;
         Address billingAddr;
         Address shippingAddr;
         float dollarAmount;
}

ComplexType CarPurchaseOrder extends PurchaseOrder {
         String model
}

Here is the service
===============

PortType POHandling {
         void submitPO(PurchaseOrder po);
}


Q1) In XML Schema, can I define another complex type "USPurchaseOrder" that 
is derived from "PurchaseOrder" ?  I want to constrain both billingAddr and 
shippingAddr in "USPurchaseOrder" to be USAddress type.

Q2) In WSDL1.2, can I pass a message of type "CarPurchaseOrder" when 
invoking the "submitPO" operation of port type "POHandling" ?

Q3) In WSDL1.2, can I define another PortType as follows ?

PortType UrgentPOHandling extends POHandling {
         String getPOStatus(String poNumber)
}

Best regards,
Ricky


>The property would be defined to be:
>
>property myBillingAddress type Address
>
>The abstract message (in the WSDL operation) would be defined to be:
>
>message someMessageType
>  sequence
>    billingAddress type Address
>    shippingAddress type Address
>    . . .
>
>The selector/alias would then express how you extract that message, for 
>example:
>
>property myBillingAddress = someMessageType/billingAddress
>
>Note that the property is still of type Address.
>
>A concrete message contain (just example):
>
>billingAddress xsi:type=USAddress
>  street  ...
>  zipcode ...
>...
>
>The value of the property instance extracted from that message would be of 
>type USAddress and would contain the zipcode. But if the concrete message 
>contained an address of type UKAddress then the property instance would 
>also contain a UKAddress with a postal code.
>
>arkin
>
>>
>>
>>Ricky
>
>
>--
>"Those who can, do; those who can't, make screenshots"
>
>----------------------------------------------------------------------
>Assaf Arkin                                          arkin@intalio.com
>Intalio Inc.                                           www.intalio.com
>The Business Process Management Company                 (650) 577 4700
>
>
>This message is intended only for the use of the Addressee and
>may contain information that is PRIVILEGED and CONFIDENTIAL.
>If you are not the intended recipient, dissemination of this
>communication is prohibited. If you have received this communication
>in error, please erase all copies of the message and its attachments
>and notify us immediately.
>
>
Received on Wednesday, 2 April 2003 13:51:30 GMT

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