Just read that as well, specifically took note of: R2003 A DESCRIPTION MUST use the XML Schema "import" statement only within the xsd:schema element of the types section.
Attempted that and .NET still choked, however, once again, +1 for Axis. Poor .NET lot -- they'll never be able to consume a service that conforms to the WS-I profile and references an external schema (not entirely true, a few several hundred megs of service packs may fix it) -- unless I'm missing something. Thanks everyone, Cory Wilkerson -----Original Message----- From: Mike Burati [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2003 12:44 PM To: '[EMAIL PROTECTED]' Subject: RE: woe the struggles of xsd:import/wsdl:import Also Note, WSI Basic Profile clarification on WSDL import vs XSD import http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#refinement3 4101304 -----Original Message----- From: Mike Burati [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2003 1:34 PM To: '[EMAIL PROTECTED]' Subject: RE: woe the struggles of xsd:import/wsdl:import Is it possible that you just need to set the content type for files of type (extension) .xsd on your server that's serving up your schema? Eg, if you're serving it up from a WAR of a J2EE server, then something like the following in web.xml <mime-mapping> <extension>xsd</extension> <mime-type>text/xml</mime-type> </mime-mapping> -----Original Message----- From: Cory Wilkerson [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2003 1:21 PM To: [EMAIL PROTECTED] Subject: woe the struggles of xsd:import/wsdl:import All, Assume xsd = http://www.w3.org/2001/XMLSchema Assume wsdl = http://schemas.xmlsoap.org/wsdl/ I've ran into quite an interesting situation with referencing external schema via xsd:import and wsdl:import. The .NET wsdl.exe tool will not generate client stubs when using xsd:import to import external schema definitions -- Axis will. Yeah for Axis. That said, Axis will not generate client stubs when using wsdl:import but .NET will. Yeah for .NET (that hurts). Specifcally, Axis can't seem to decipher the content-type when importing schema: ----------------- STACK TRACE ----------------- [java] WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported doc ument at 'http://10.10.4.75:8001/foo/HotelCity.xsd'.: no content-type: java.net. UnknownServiceException: no content-type [java] at java.net.URLConnection.getContentHandler(URLConnection.java:1 059) [java] at java.net.URLConnection.getContent(URLConnection.java:583) [java] at java.net.URL.getContent(URL.java:969) [java] at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Sour Has anyone else encountered the above? I'd like to generate WSDL that imports schema and works across client tools -- but the above is prohibiting that. I'd take this up with the Micorosoft folk as well, but they'd never listen. Thanks, Cory Wilkerson
