-
Notifications
You must be signed in to change notification settings - Fork 267
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
Can not parse WSDL file with yaws_soap_lib #65
Comments
I'm currently discussing your issue with the author of erlsom, and we're trying to figure out if we can address this and if so what best way to do it would be. Stay tuned. |
Allow to pass options to erlsom (fix issue #65)
Please try out Willem's changes, they should allow you to do what you're trying to do. Let us know how it goes. |
I've just tried it with newly pulled version but the problem still exists. The only difference I can see are the arities of functions in stack trace:
|
You need to make your call differently, which is why Willem made the changes he made. Hopefully Willem will chime in with specific instructions for you. |
Yes, Steve is right. The changes I made allow you to pass a list of options to yaws_soap_lib:initModel(). These options will be passed on to erlsom. One of them can be a reference to a function that fetches the included XSDs. You can find more about it in the erlsom documentation. In your case, you might try to pass it a reference to a function called find_xsd() in erlsom_lib. Your call could look something like this: yaws_soap_lib:initModel(WSDL_FILE_URL, [{include_fun, {yaws_soap_lib, find_xsd}}]) - I can't guarantee that this will work, but it should be enough to get you started, I hope. |
OK, I've managed to build model with following command:
Thanks! |
Allow to pass options to erlsom (fix issue erlyaws#65)
I've been trying to use YAWS' SOAP lib (old version, can't remember which one) to parse a WSDL file and invoke service operation. However, I could not parse the WSDL property. The WSDL itself is valid (tested on multiple on-line validators). Probably the problem was an empty tag in the WSDL file. Details are here: http://stackoverflow.com/questions/5404926/wsdl-empty-types-tag-and-yaws-soap-support
Right now I am trying to do the same with 1.9.1 version and erlsom 1.2.1. Unfortunately I had no luck. It appears to me that yaws is trying to include files that are not existent (such as soap.xsd, wsdl.xsl) and erlsom can't handle that. The commands I am invoking:
the error:
Both urls are available through HTTP
The text was updated successfully, but these errors were encountered: