-
Notifications
You must be signed in to change notification settings - Fork 242
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
The empty arguments problem. #8
Comments
Right. That's a bug in Nori rubiii/nori#12. I'll try to produce workaround for now. |
Okay. Look what we got. I did the workaround and that solved the problem for all non-ruby SOAP clients. However Savon uses Nori too. And therefore it's a subject for the same bug on the client. If you don't use Savon you are good to go. Please check |
Fixed in 0.3.2 |
Thank you. |
I'm currently having the same problem as described in this issue again:
My environment: wash_out in version 0.9.0, nori in 2.4.0, ruby 2.1.2 / rails 4.1.4, soap ui as client in version 4.6.4-m-SNAPSHOT |
Hi!
I have the following code
in my api controller
soap_action "BlockAccount",
:args => {:ils => :string, :asr_id => :string},
:return => {:asr_id => :string, :ils => :string},
:to => :block_account
def block_account
render :soap => {:ils => params[:ils], :asr_id => params[:asr_id]}
end
The request to the my service,
response
it works fine, but
the request with empty arguments
response
The value '{:"@xsi:type"=>"xsd:string"}' is unexpected for me.
When I get the request with empty argument, params[:argument] returns "{:"@xsi:type"=>"xsd:string"}'.
The text was updated successfully, but these errors were encountered: