2

I have a WSDL doc with XSD import.

 <xsd:import namespace="http://site.com" schemaLocation="schema.xsd"/>

WSDL tool assumes that schema is in the same directory, but load fails in rails with error

 <RuntimeError: Unable to find schema for "http://site.com">

I've tried write path from rails root and from system root, but with no success.

I use Savon 3 to deal with WSDL in rails. SoapUI works with this schemas normally.

So, what is the right way to write this path?

Kirill Fedyanin
  • 572
  • 5
  • 22
  • Kirill, which version of savon? It behaves really really different from version to version – Ivan Shamatov Oct 22 '13 at 13:10
  • 1
    I am not so familiar with the toolset you've described, but did hear a lot of limitations in connection with stacks such as yours. If your referenced XSDs DO NOT USE xsd:include, then, if it's not that much to do, try to inline all the XSDs (i.e. copy their content) inside the WSDL file, then make sure you remove all the schemaLocation attributes of all the schema imports and run again. Many tools in my past experience failed miserably when XSDs are all over the place, but worked when all content is embedded in one WSDL file. – Petru Gardea Oct 22 '13 at 13:13
  • It appears that inlining doesn't help so much in this case, as xsd:import suggests namespace usage and you can have only single namespace in single xsd file. I've solved my problem by placing files online and make absolute url path. It's rather poor decision, but it works. (This comment is mostly for future reference) – Kirill Fedyanin Oct 30 '13 at 16:24

0 Answers0