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

When using use="literal" in soap types not getting converted #628

Closed
maxstudener opened this issue Oct 8, 2014 · 4 comments
Closed

When using use="literal" in soap types not getting converted #628

maxstudener opened this issue Oct 8, 2014 · 4 comments

Comments

@maxstudener
Copy link

Types are all defined in wsdl but only uses nori advanced typecasting. This only converts booleans and dates and times, I reported this where i think it needs to be fixed savonrb/nori#66 . This reallllly gets crazy when you have a complex object and it has an array type and if there is only one object nested [thing][thing].is_a?(Hash) but if there is multiple objects its [thing][thing].is_a?(Array). While reading through the source code i don't really see anything anywhere caring about the types defined in the wsdl.

@maxstudener
Copy link
Author

I see that client.instance_variable_get(:@wsdl).parser.types has all the thats in it but it is getting lost someone on the response object

@maxstudener
Copy link
Author

Looks like it would be possible to pass the wsdl to create_response on the operation class method and then you could pass it into Nori.new and update the nori gem to use those types in the wsdl parse types to ruby types

@stale
Copy link

stale bot commented Feb 19, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 19, 2018
@stale
Copy link

stale bot commented Feb 26, 2018

This issue is now closed due to inactivity. If you believe this needs further action, please re-open to discuss.

@stale stale bot closed this as completed Feb 26, 2018
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

1 participant