W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > September 2006

RE: ISSUE-68: xs:import of Schema 1.0 namespace

From: George Cowe <gcowe@origoservices.com>
Date: Wed, 20 Sep 2006 13:34:06 +0100
Message-ID: <DC65AE678B89004B9CCB202E19482CC70165233C@mail.origoservices.local>
To: public-xsd-databinding@w3.org

Interestingly both the IBM and Axis tools report WS-I compliance problems with echoImportSchema.wsdl
 
WS-I: (BP2102) An XML schema import element references something other 
than an XML schema definition: the referenced element does not have 
"schema" from XML namespace "http://www.w3.org/2001/XMLSchema" as root 
element.

WS-I: (BP2122) A wsdl:types element contained a data type 
definition that is not an XML schema definition.	

If we are going to be WS-I Basic Profile compliant then we need a schemaLocation. 

George  


-----Original Message-----
From: public-xsd-databinding-request@w3.org [mailto:public-xsd-databinding-request@w3.org] On Behalf Of paul.downey@bt.com
Sent: 19 September 2006 15:00
To: public-xsd-databinding@w3.org
Subject: ISSUE-68: xs:import of Schema 1.0 namespace


i've tested:

http://www.w3.org/2002/ws/databinding/examples/6/05/ImportSchema/echoImportSchema.wsdl

with a few different toolkits, notably:
Apache Axis 1.3, BEA Weblogic Server 8.1,
IBM WebSphere 6.0, Microsoft .NET 1.1 C# 	 		
Microsoft .NET 2.0 C#, SOAP4r 20051204 (Ruby) 
and Mono _1.1.13.8 C# 

The only one to barf was the IBM kit, 
I'm not confident that's the kit or my fault
maybe someone could double-check my results?

Paul
Received on Thursday, 21 September 2006 15:17:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:20:37 GMT