-
Notifications
You must be signed in to change notification settings - Fork 615
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
Config setting for WSDL-free operation (alternative to switching all calls to method_name! syntax) #76
Comments
(now I think about it, these could easily be per-instance options for the Savon::Client constructor, rather than global config) |
this was a bad design decision, but it was easy to implement back then. the next version is going to change this! |
Nice one. |
this should be fixed in the current dev branch. there's still some refactoring left to do, but i hope to get this released asap. |
please try savon 0.8.0.beta.1 |
BTW, when there is no wsdl the soap action header might have to be set manually (in my case talking to a .NET web service):
Might want to add this example to the user guide. |
released v0.8.0 which should solve this problem. |
You say:
But in order to switch to this approach in production it appears necessary to add an exclamation mark to all method calls.
Would be nice if you could instead just set some config in production, eg:
or even:
which would cause it to ignore any WSDL URL passed to the constructor, and treat all methods in the wsdl-free way.
The text was updated successfully, but these errors were encountered: