Quarts and quarts of Java alphabet soup including a complete specification for webservice meta data. A programmer like me who knows what SOAP is and is holding a complete specification for a webservice should be able to build a Java client that talks to it within minutes. Instead, hours later, I'm still looking through docs and books and despairing. What's the point of WSDL if there's not some simple way to feed it to a program or a class and receive as output an object that speaks the specific webservice and provides all of its methods? And if I can do that, why isn't it the first thing I found when I started looking?
This isn't rocket science. True I've never programmed SOAP, but I've done other RPC systems, and I understand XML, and I even have a vague idea what RESTful means. I don't need any complicated instructions on how to write the webservice server; I have access to a machine-readable description of what it does, what methods it provides, and what parameters they take. There should be some trivial mechanism for feeding that description into something and being up and running within seconds. Where is it??
Re:The SYNOPSIS should always be kept in mind
lachoy on 2008-05-07T05:52:25
I've been wrestling with the server-side part of this. On the client-side I found the soapUI tool excellent, and this set of instructions on setting up a client, while lengthy, seems pretty straightforward.
