[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Famous web services with apparent serious XML schema error

famous web

> I'm working on an application that needs to be able to read and rely on
> XML Schema information contained in or referenced from web service
> descriptions (WSDL), since it is supposed to be able to dynamically
> with any web service so specified.  While this is possible with many web
> services, it seems that developers of these descriptions sometimes
> a common set of what I believe to be erroneous schema constructs and
> The the schemas are
> a.  invalid
> b.  fail to define the types that were intended
> and the instances returned from the web services are invalid with respect
> the schemas.
> The common errors (if I am not confused!) are:
> 1.  Using the http://schemas.xmlsoap.org/soap/encoding/ namespace (the URL
> can be dereferenced to get the schema) and referring to its types without
> <import> in the schema.  The schema thus will not be accepted by a schema
> validator.

Yes, it's common.

> 2.  Definition of array types based on the soap encoding, like this:
> <xsd:complexType name="AuthorArray">
>     <xsd:complexContent>
>      <xsd:restriction base="soapenc:Array">
>       <xsd:attribute ref="soapenc:arrayType"
>      </xsd:restriction>
>     </xsd:complexContent>
> This derivation fails to copy the unchanged content from soapenc:Array
> (basically a repeating <any>), so instead of defining a homogeous array,
> specifies empty content..[1]  Xerces tells me so when I hand it an

This manner of  "derivation" is found in the WSDL 1.1 spec. See bullet three


and look at examples such as Example 5. An often cited critique of this can
be found within:


This has been the cause of quite a bit of debate in the past on various
lists. The consensus by implementors of WSDL processors seems to be to adopt
it as given in the WSDL 1.1 spec for until something better comes along. The
argument was that the definition for a SOAP encoded array wasn't to be used
for validation. A typical expression of this pov is found at:




Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.