Wasabi does not handle wsdl import

[emeka]

Hi,

I have the following wsdl document:

<definitions xmlns:interface="urn:vbox" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:vbox="http://www.virtualbox.org/" xmlns="http://schemas.xmlsoap.org/wsdl/" name="VirtualBox" targetNamespace="http://www.virtualbox.org/Service">
  <import location="vboxweb.wsdl" namespace="http://www.virtualbox.org/"/>
  <service name="vboxService">
    <port binding="vbox:vboxBinding" name="vboxServicePort">
      <soap:address location="http://localhost:18083/"/>
    </port>
  </service>
</definitions>

It imports an other wsdl file called 'vboxweb.wsdl' which is located in the same directory and which contains all the type and message definitions.

Unfortunately, the imported file is not handled by wasabi.

Regards,

Emeka

[rubiii]

you're right, wasabi doesn't follow import statements. it's something i'm working on from time to time, but it's not ready yet.

[hoverlover]

Yeah, I have a wsdl that defines import inside of /definitions/types/schema. Any word on when this might be added to wasabi?

[rubiii]

unfortunately no. a decent wsdl parser is not that hard to write, but parsing the xs schema is kinda difficult. i'm still working on it and will let you know when i have something to show.

[emeka]

Thanks for the good work.

Emeka

On 17 February 2012 13:00, Daniel Harrington reply@reply.github.com wrote:

unfortunately no. a decent wsdl parser is not that hard to write, but parsing the xs schema is kinda difficult. i'm still working on it and will let you know when i have something to show.

---

Reply to this email directly or view it on GitHub: https://github.com/rubiii/wasabi/issues/1#issuecomment-4019736

[rubiii]

still no decent support for imports. if anyone wants to give it a go ...

[MattRogish]

+1

[rubiii]

master contains a major rewrite which is not done yet, but already supports wsdl imports. xml schema imports should be supported soon. if you can, please give it a try. i updated the readme to reflect the new interface.

[krisleech]

Is import expected to work when the wdsl is a local file and contains a location such as:

<import namespace="http://www.travelport.com/service/hotel_v21_0" location="HotelAbstract.wsdl"/>

I get No such file or directory - HotelAbstract.wsdl.

I'm using the latest master branch.

[rubiii]

@krisleech the first step only supports fully qualified import locations. i haven't found any information about whether relative URL's are even valid. if they are, it would be good to have a specification for it.

ps. i'll add it to the todo-list.

[krisleech]

I don't know nearly enough about SOAP to know if rel URL's are legit, just that my WDSL has them :) Luckily our client decided not to use the SOAP API in question after discussing the alternative options (JRuby + something).

I've used Savon before, its been a life saver, so thanks for taking the time!

[rubiii]

thanks @krisleech