Skip to content
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

Closed
mjwillson opened this issue Aug 11, 2010 · 7 comments

Comments

@mjwillson
Copy link

You say:

For production, it is highly recommended to not use Savon::WSDL

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:

Savon::Client.wsdl_free_method_calls = true

or even:

Savon::Client.skip_wsdl_loading = true

which would cause it to ignore any WSDL URL passed to the constructor, and treat all methods in the wsdl-free way.

@mjwillson
Copy link
Author

(now I think about it, these could easily be per-instance options for the Savon::Client constructor, rather than global config)

@rubiii
Copy link
Contributor

rubiii commented Sep 11, 2010

this was a bad design decision, but it was easy to implement back then. the next version is going to change this!

@mjwillson
Copy link
Author

Nice one.

@rubiii
Copy link
Contributor

rubiii commented Sep 26, 2010

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.

@rubiii
Copy link
Contributor

rubiii commented Oct 29, 2010

please try savon 0.8.0.beta.1

@ghost
Copy link

ghost commented Dec 14, 2010

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):

action = method_name.to_s.camelize
response = client.request(:wsdl, action) do
  http.headers['SOAPAction'] = 'http://example.com/webfront/IWebFront/' + action
  soap.body = params
end

Might want to add this example to the user guide.

@rubiii
Copy link
Contributor

rubiii commented Dec 20, 2010

released v0.8.0 which should solve this problem.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants