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

RE: Schemas in imported WSDL

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Fri, 14 Nov 2003 12:00:12 -0800
Message-ID: <DD35CC66F54D8248B6E04232892B6338621589@RED-MSG-43.redmond.corp.microsoft.com>
To: "Glen Daniels" <gdaniels@sonicsoftware.com>, "Jacek Kopecky" <jacek.kopecky@systinet.com>, "Amelia A. Lewis" <alewis@tibco.com>
Cc: <tomj@macromedia.com>, <abrookes@roguewave.com>, "WS-Description WG" <www-ws-desc@w3.org>

Hang on. The case Jacek has listed below SHOULD work. Why? Because WSDL
A has EXPLICITLY imported that namespace. And the WSDL processor that's
dealing with WSDL A and WSDL B can use the schema from WSDL B to satisfy
the import in WSDL A.

Gudge

> -----Original Message-----
> From: Glen Daniels [mailto:gdaniels@sonicsoftware.com] 
> Sent: 14 November 2003 08:05
> To: Jacek Kopecky; Amelia A. Lewis
> Cc: Martin Gudgin; tomj@macromedia.com; 
> abrookes@roguewave.com; WS-Description WG
> Subject: Re: Schemas in imported WSDL
> 
> > I also agree on the semantics as far as Gudge formulated it.
> >
> > But I thought WSDL A can use schema C inlined in WSDL B if WSDL A 
> > wsdl:imports WSDL B and xs:imports schema C (probably omitting the 
> > location attribute).
> 
> That was pretty much the jist of the conversation we had at 
> the F2F; whether or not there should be any guarantee of 
> being able to do just that.  Apparently the answer is "no", though.
> 
> --G
> 
> 
> 
Received on Friday, 14 November 2003 15:00:15 GMT

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