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

NoMethodError: undefined method `invalid!' for Savon::WSDL #2

Closed
nbibler opened this issue Nov 30, 2009 · 4 comments
Closed

NoMethodError: undefined method `invalid!' for Savon::WSDL #2

nbibler opened this issue Nov 30, 2009 · 4 comments

Comments

@nbibler
Copy link

nbibler commented Nov 30, 2009

If the WSDL meets the "invalid" criteria when loading, Savon attempts to call an "invalid!" method that does not appear to be defined in the current gem (0.5.2).

require 'savon'
proxy = Savon::Client.new "https://test-api.geotrust.com/webtrust/query.jws?WSDL"
proxy.wsdl.soap_actions

D, [2009-11-30T15:58:46.389373 #40297] DEBUG -- : Retrieving WSDL from: https://test-api.geotrust.com/webtrust/query.jws?WSDL
warning: peer certificate won't be verified in this SSL session
NoMethodError: undefined method `invalid!' for #<Savon::WSDL:0x102319540>
    from /Library/Ruby/Gems/1.8/gems/savon-0.5.2/lib/savon/wsdl.rb:44:in `wsdl_response'
@rubiii
Copy link
Contributor

rubiii commented Nov 30, 2009

@rubiii
Copy link
Contributor

rubiii commented Nov 30, 2009

ohh and thanks for letting me know about this issue!

@corny
Copy link

corny commented Jan 19, 2010

The NoMethodError is fixed, but in version 0.7.2 proxy.wsdl.soap_actions is still empty. please check out by patch:
http://gist.github.com/280877

@rubiii
Copy link
Contributor

rubiii commented Jan 19, 2010

thanks for taking the time to submit a patch. but i would prefer if you could fork the dev branch of savon, add your patch and tests(!) and send me a pull request. this way i can assure your patch does not break any existing wsdl documents. cause appart from your wsdl, it parses dozens of others just fine.

also if you could add you wsdl document to the test fixtures, all users would benefit from your patch. of course you can mask actual uri's, company names and such.

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

3 participants