If you are talking about WSDL.exe the way that io jave been able to deal with that is to pass in all the imported XSD files at the command line in addition to the wsdl file.
--Danno Tony Opatha <[EMAIL PROTECTED]> wrote: __________ > >I don't see any requirement in WS-I BP 1.0a that specifies that imported XSDs > >can not import additional XSDs. However, it is reasonable to allow WSDL > >to import other .wsdl's. > > > >BTW, I believe .NET 1.1 Framework/VS.NET 2003 WSDL processor > >does not resolve multiple imported XSDs, hence you have to have > >a WSDL importing another WSDL which contains type definition > >pertaining to your original XSD schemas. Major limitation on .NET > >which may hinder how you publish your public interfaces and > >schema components using AXIS.... > > > > > >-----Original Message----- > >From: Jim Murphy [mailto:[EMAIL PROTECTED] > >Sent: Thursday, January 22, 2004 12:17 PM > >To: [EMAIL PROTECTED] > >Subject: Re: Regarding importing XML Schema files... > > > >Unfortunately the WS-I doesn't like that very much. :) The WS-I BP 1.0 > >says WSDL imports can only import other WSDL documents. You can put a > >dummy wsdl:type/xsd:schema section that imports these directly. > >--- message truncated ---
