On 12/6/06, Jeff <cohen.jeff / gmail.com> wrote:

> Why not publish a REST interface instead?
...
> The Soap garbage just gets in the way, in my very humble opinion :-)

True enough!

snacktime wrote:
>
> He should really be using rails and actionwebservice, it makes this
> much easier.
...

Right, thanks for the tip.  When I was looking into WSDL support, I
came across that, but I wanted to see if I could still do it without
Rails.  I'm really only exploring this option to see if it could work,
and I'm not particularly serious about using it. :)  Mainly I was
wondering if anyone else had done this sort of thing or if there was
some SOAP guru who could point out exactly why my .NET client doesn't
like the response that it's getting.  Of course, opinions like these on
what I should be doing instead are most welcome.