Philippe Jacot <leschagg <at> gmail.com> writes:
>
> I'm using JaxbWSDLBuilder to create the WSDL for a webservice. As long
> as I'm using types from a single namespace there are no problems, but
> when I use different namespaces the WSDLBuilder creates a file that
> contains tags like <xs:import schemaLocation="
> schema2.xsd" />. Although the content of schema2.xsd is also found
> in the WSDL, I cannot parse such a file as I get the exception attached
> below. Obviously the file schema2.xsd cannot be located.Is there a way to tell
XFire not to add the <xs:import> or not to resolve imports relative to the
current position?
I have the same problem. My WSDL imports a schema in a nested folder and that
schema in turn imports another schema in the same folder. The first nested
schema is read correctly, but the relative import then fails because it is using
the original path, not the nested one.
Terry
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
