-
Notifications
You must be signed in to change notification settings - Fork 616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested Namespace ~ imported wsdl #532
Comments
Hey @stanl3y ! This would be a really great thing to support, since a fair amount of WSDLs actually have this. In the currently supported version of Savon (2.3.2), parsing WSDLs (and imported WSDLs in particular) are handled by [Wasabi][https://github.com/savonrb/wasabi). There's an open issue there to support this that I'd love to close someday soon. (Yes, it's literally issue number 1) If you'd like to take a shot at writing a pull request for Wasabi, I'd be more than happy to help provide some context for that code and to help figure out what the correct solution is for your WSDL. Taking a look at your wsdl... I'd have to guess that maybe the problem is the relative path for location of the imported wsdl. That's a neat weird edge case that the current code probably does not handle. |
Sorry if this has been answered but wanted to know if this was ever fixed? |
Hey @phspies, I regret to inform you that it is still an open issue. In fact, it's open issue # 1 on Wasabi. |
Hello !
I am trying to use this webservice,
http://publicbetawebservices.hotel.de/V2_8/FreeHotelSearchWebService.svc?WSDL
which imports the wsdl from here
http://publicbetawebservices.hotel.de/V2_8/FreeHotelSearchWebService_ServiceContract.wsdl
Using SoapUI, I can get this template and it works fine.
While when using Savon
I obtain the following. Please note the v2 namespace goes one level only. Is there a way to make it same as above without typing manually?
The text was updated successfully, but these errors were encountered: