What would some of the steps be to convert a Java Class to a webservice? I am assuming that an SEI(Service EndPoint Interface) needs to be created from the Java class or the Interface and then create the WSDL using a tool. Once could go the other way too right?My idea is to get your views.
That depends on your level of WS skills. It could be as simple as renaming a .java file to .jws and throwing it into the Axis directory of your servlet container (see this for details). This mechanism has many drawbacks that makes it unsuitable for production WS, but it does get you going quickly.
Originally posted by Romario Dominic: In regular WebService applications,SOAP is commonly used as the messaging protocol right? Now is there any other protocol which is as useful?
SOAP tries to fulfill many requirements which makes it a fairly heavy-weight technology. SOAP and WSDL have been and continue to be standardized, so it's relatively simple to build tools that utilize them. Often SOAP/WSDL ends up being an overkill solution to some of the problems that its being applied to - simply because the tools at hand made it "relatively simple" to set up.
For RPC you can always consider these technologies:
Then there is REST (Representational State Transfer) which isn't a protocol or technology - it's an architectural style. REST-style web services are IMHO much better suited to supporting AJAX-clients (for example) than heavy-weight SOAP Web Services. However there is no "standard" - it's a style, so tool vendors can't directly support (or exploit) it, consequently it never got as much press as SOAP. Building Web Services the REST Way Implementing REST Web Services: Best Practices and Guidelines