axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Perham" <>
Subject RE: woe the struggles of xsd:import/wsdl:import
Date Mon, 25 Aug 2003 18:14:40 GMT
Sounds like the server needs to add a Content-Type header when returning
an XSD document.  Depending on the server, this may be as simple as
adding some MIME configuration so *.xsd maps to "text/xml".

-----Original Message-----
From: Cory Wilkerson [] 
Sent: Monday, August 25, 2003 12:21 PM
Subject: woe the struggles of xsd:import/wsdl:import


Assume xsd  =
Assume 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

     [java] WSDLException: faultCode=OTHER_ERROR: Unable to resolve
imported doc ument at ''.: no
UnknownServiceException: no content-type
     [java]     at
     [java]     at
     [java]     at
     [java]     at
     [java]     at
     [java]     at 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.  

Cory Wilkerson

View raw message