-
Notifications
You must be signed in to change notification settings - Fork 614
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
Version 1.2.0 generate invalid body XML from hashes. #321
Comments
would it be possible to provide the WSDL document you are using so that I can reproduce these errors? |
ok, the wsdl is in this public Gist git://gist.github.com/3744255.git or |
great, I'll take a look as soon as I can, thanks. |
hey @skoona, the good news is, i found out why savon creates a nil-tag for regarding the try to add a |
pushed the fix. this will be included in the next release. thank you for reporting this problem. |
rubiii, I am able to confirm that #to_s on booleans formats the xml correctly. As a result I've upgraded to Savon 2.0.2 with only the required refactoring (i.e replace Savon.config and client request format.) Thanks for your help. |
awesome 😄 |
This was fixed in savonrb#321, commit aa3ae5d however it snuck back into the code. This fixes it again.
Question: Help me understand how to fix these problem, or should I just wait for the next update?
It doesn't work is the wrong way to start any bug report; but it does accurately indicate how confused I am in trying to describe the failures I see. I'm using savon in a rails 3.2.7 application under development and I wrote the web services routines two months ago and covered them with rspec tests. Those tests suddenly failed last nite, as a result of a 'bundle update' causing the savon version to move to 1.2.0.
I see two errors types which seem to be caused by a hash_to_xml conversion.
Example (A) below is the output generated by version 1.1.0, and example (B) is the output from version 1.2.0. Example be causes a soap fault. The following is a snippet from the savon call.
example (A) Good
example (B) Bad
The text was updated successfully, but these errors were encountered: