I ran in exactly the same problem and found the cause: The SOAP request was redirected because of a configuration problem and some HTML was returned. That HTML did not get through the response parser, what is no surprise.
Yep, in my case it was a result of some routing issue, that got caught in the routing change in r3636. I don't know routes well enough to sort it out, so I just hacked it to go back to the old functionality (which just ignored all NameError's as it resolved the route).
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
