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

RE: wsdl:types and arrays

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Mon, 2 Dec 2002 11:26:01 -0800
Message-ID: <92456F6B84D1324C943905BEEAE0278E02F443B0@RED-MSG-10.redmond.corp.microsoft.com>
To: <mats_henricson@yahoo.com>, <www-ws-desc@w3.org>

Hi Matt,

Can you point me to the language in the WSDL 1.2 spec that leads you to
believe that you can't use maxOccurs on an element declaration in WSDL?
AFAIR that it was NOT the WGs intention to have such a limitation.

I'll take info on 1.1 aswell but we're not revving that document.

Cheers 

Gudge

> -----Original Message-----
> From: Mats Henricson [mailto:mats_henricson@yahoo.com] 
> Sent: 29 November 2002 23:21
> To: www-ws-desc@w3.org
> Subject: wsdl:types and arrays
> 
> 
> 
> 
> 
> 
> Hi, all!
> 
> I was pretty enthusiastic about using web services, SOAP
> and WSDL, until I realized the severe XSD limitation in WSDL.
> I have a 4 page long XSD, and a 200 kB long hand-written XML 
> document that follows that XSD. According to the WSDL 1.1 and 
> 1.2 I can't use this XSD construct:
> 
>   <xsd:element ... maxOccurs="unbounded"/>
> 
> I just barely can believe this limitation really exists!
> I would have to do heavy changes of my large XML document
> just to be able to use SOAP?!
> 
> Pretty much every single XSD tutorial out there suggests
> the use of maxOccurs="unbounded".
> 
> Is it really true that it can't be used in WSDL, or have I 
> totally misunderstood? If that limitation really exists, why 
> don't you remove it in this new upcoming version of WSDL?
> 
> Worried greetings from
> 
> Mats Henricson
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now. 
http://mailplus.yahoo.com
Received on Monday, 2 December 2002 14:26:33 GMT

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