Simon, the reason why I'm a WSDL FM fan is simple:
I guess that SOAP & web services in general will only really take off as soon as they are absolutely easy to use. For me, Radio together with WSDL FM was easy to use.
Let's recap the steps necessary to make Radio talk to .NET Remoting:
- Write the .NET Remoting Web Service and start the server
- Run WSDL FM and point it to the (automatically generated) WSDL
- Write <% someservice.someMethod() %> in Radio
I did never ever have to know about SoapActions, method namespaces or anything like this. The tools (.NET Remoting on the server side and WSDL FM on the client) took care of this for me.
I think this tool support will be essential for the success of web services. Developer's shouldn't have to worry about those kind of "internals". They should instead care about solving their application domain specific issues. We need those kinds of tools for other platforms and languages (compilers and scripting) as well!
You might also want to compare this with other (manual) approaches - IMHO there are too many possibilities of problems with those.
This, Dave, is the real reason why I believe that we need WSDL for our web services.
Comments