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

input_for in parser.rb raising NoMethodError #11

Closed
cschiewek opened this issue Jul 4, 2012 · 4 comments
Closed

input_for in parser.rb raising NoMethodError #11

cschiewek opened this issue Jul 4, 2012 · 4 comments
Labels

Comments

@cschiewek
Copy link

I'm getting the following error:

NoMethodError: undefined method `attribute' for nil:NilClass
    from wasabi-2.5.0/lib/wasabi/parser.rb:156:in `input_for'
    from wasabi-2.5.0/lib/wasabi/parser.rb:92:in `block in parse_operations'

When calling pretty much any method on a document object (namespace, soap_actions, operations, etc). Here is the WSDL that causes the problem: http://sudbury.production.its4mobility.com/Tmix.Cap.Ti/1.3.4/TrafficInformationService.svc?wsdl

I'm not overly familiar with WSDL, but SOAPUI is having no problems parsing it.

Thanks!

@rubiii
Copy link
Contributor

rubiii commented Jul 4, 2012

soapUI probably has the best wsdl/xsd parser i've ever seen. so i'm not surprised that it works :)
thanks for providing the wsdl. i'll look into this later today or tomorrow.

could you let me know which versions of savon and its direct dependencies you're using?

@cschiewek
Copy link
Author

I initially ran into the issue using savon 1.1.0, and then tested it directly with wasabi 2.5.0 (which was using nokogiri 1.5.4) and got the same result. Thanks!

@rubiii
Copy link
Contributor

rubiii commented Jul 26, 2012

thanks for the effort you put into this, but i fear the solution for this is not that easy. i just downloaded your original
wsdl file and all of its xsd imports. as it turns out, the wsdl actually contains a portType element, but it's "hidden" in
one of those imports.

the problem here is, that the current parser does not support imports and therefore can't handle the wsdl.
this is a problem that i aim to fix with the new sax parser. for now, i would suggest to not use the wsdl at all.

ps. there's an open issue #1 to track the progress of this feature.

@rubiii rubiii closed this as completed Jul 26, 2012
@cschiewek
Copy link
Author

Sounds good to me. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants