Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

  (email not shown publicly)

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Tuesday May 06, 2008
02:21 PM

Java web services

[ #36340 ]

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??

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.