Savon doesn't follow xsd:import in wsdl's xsd:schema

[kjg]

For example https://ws5.responsys.net/webservices/wsdl/ResponsysWS_Level1.wsdl contains the following, but doesn't pull in and evaluate the resources at the specified schemaLocations.

<xsd:schema>
    <xsd:import namespace="urn:ws.rsys.com" schemaLocation="../services/ResponsysWSService/_resources_/xsd/ResponsysWSTypes_Schema.xsd"/>
</xsd:schema>
<xsd:schema>
    <xsd:import namespace="urn:fault.ws.rsys.com" schemaLocation="../services/ResponsysWSService/_resources_/xsd/ResponsysWSFaults_Schema.xsd"/>
</xsd:schema>

[rubiii]

you're right. in lack of a decent wsdl/xsd parser, savon uses wasabi, which is a very simple parser and one of the feature it lacks is support for wsdl imports. i guess it wouldn't be too difficult to support it, but i simply haven't had the time to do it.

[rubiii]

closing this as it's stale. if you can help fixing this issue, please let me know.

[rajeev-sourcebits]

Was this feature of supporting wsdl:imports included in the LIbrary ?
If not, what is the workaround I can use to support SOAP Services with wsdl:imports.

Thanks
Rajeev

[rubiii]

version 3.0 is supposed to finally solve this.
everyone: please follow savonrb/wasabi#27 for now.

[rubiii]

the milestone ticket for version 3 is #473 and initial documentation for version 3 is online.
both wsdl and xml schema imports are already supported. please give it a try and report any problems.

[rubiii]

fyi: it's possible to work around this problem. if savon can't find the types due to imports, you may need to handle things like namespaces yourself. please read up on how you can use gyoku to create a request hash that matches an example request generated by soapUI.

ps. and learn about namespaces. namespace identifiers don't mean anything. compare their values. end of rant ;)

[rajeev-sourcebits]

👍