Object reference not set to an instance of an object.

[cambridgemike]

I'm not convinced this is an issue with Savon, but rather my struggling with the Soap in general. Maybe you will have a suggestion though.

I set up the XML and made the request using Savon. The request returned a SOAPFault, server error 500 with an error message "Object reference not set to an instance of an object." I had seen this before when i was missing required fields in the XML, so I copy and pasted the entire soap envelope into SoapUI and made the request. it worked perfectly from SoapUI though. Why would the request work in SoapUI but not through Savon? What other variables are there besides the contents of the envelope that I can use to debug this?

thanks in advance

mike

[rubiii]

sounds weird. you could also compare if the http header generated by savon and soapUI are the same. if you can't find the problem, you could send me the logs from a soap call request and response as well as your soap-call-code (incl. your wsdl endpoint) and i'll have a look.

[cambridgemike]

Hi, I sent you a message with some snippets of the log files (seemed a little long to post here).

Cheers,
mike

[rubiii]

saw it, but it looks ok to me. so i really don't know where to continue here. access to make a successful soap request might be helpful. don't know if that's possible though.

[subakva]

I just saw the same error while trying to access a .Net web service. I noticed that SoapUI defined a namespace for the service and used it for every element. Savon adds a namespace called "wsdl" to the request that I needed to use on each element in my request.

client = Savon::Client.new "http://example.com/danceparty?wsdl"
response = client.get_down do |soap|
  soap.body = {
    'wsdl:battle' => {
      'wsdl:style' => 'krump'
    }
  }
end

[rubiii]

that's correct. up until now savon does not set namespaces automatically. that's why you can use string keys to make it work.

[cambridgemike]

I think I might have found a clue to get this working for me. I followed this code snippet to make the SOAP request from ruby http://broadcast.oreilly.com/2008/12/creating-custom-soap-requests.html (it just makes the net-http request), and it failed in the same way that savon was failing. I think copied over to my manual approach everything that was in the header of the SOAP UI request, and it worked! It turned out having the 'user-agent' set was important.

Would it be possible to open the http header to the end user?

thanks,
mike

[rubiii]

hey mike,

the http object will be made public in the upcoming release. so you'll be able to set timeouts and everything else directly on the net::http instance. going to release it this weekend.

cheers,
daniel

[rubiii]

just released version 0.7.0. please refer to the changelog and wiki for information about how to access the http object and let me know if this works for you.

[rubiii]

closing the issue. please reopen if this does not work.