how frequently does the letter e appear in:
from the corporation to the cloud, today more and more people are talking about web services. indeed, whilst most folks understandably feel that get, post, and html have certainly been serving us all rather well, the hottest trend in recent memory is to provide xml-based web services.
a few years back soap based services were so hot that ibm, microsoft, and xmethods all provided phone-book type repositories for 3rd part web services. today however, the last standing place to go for free-and-open independent web services remains the same as before the others came and went: xmethods.org.
for the sake of efficiency, the current underpinnings for web service delivery is decidedly moving away from fat-and-chatty xml-centric content-exchange. yet while conventions such as rest and json offer very real performance alternatives to soap, when it come to exchanging service definitions, xml remains king.
since the new crop of xml-defined web services are at the heart of everything from soa to esb, whenever there is an interest in a class i like to present a short meandering past the wsdl workings of xmethods. while i have hosted a few services there myself, since microsofts second msxml melt-down, in class my students and i like to use a free stock quote service.
of course, the best part of defining services in xml is that once we paste the endpoint (or - depending upon the ide - the xml document itself) that code can be generated.
the rest is academic - but the above is an example of how to use one of the many xmethods web services under eclipse.
user
There are one hundred and ninety-seven "e"s.
assistant