--
You received this message because you are subscribed to the Google Groups "Columbus Ruby Brigade" group.
To post to this group, send email to colum...@googlegroups.com.
To unsubscribe from this group, send email to columbusrb+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/columbusrb?hl=en.
As a long time .NET developer I can say that if they are generating
their SOAP services via the Web Reference style then the resulting
generated services are going to be expecting values that soap4r does
not contain. If possible, ask them if they are establishing their
service with WCF (.NET 3.0+). If so, ask them to configure the REST
endpoints as well and those will play much better with what you'd
expect in Rails with minimal effort on their part.
This issue was common for all clients (around the .NET 2.0 timeframe)
that were not generated explicitly by Visual Studio.
Again, I don't know if that helps, hurts, or makes you just shrug but
I thought I mention it as a possible, low cost solution to the issue
that provides value to both parties involved. Thanks!
Leon Gersing
Software Artisan, EdgeCase LLC