Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

WebServices clarifications!!  RSS feed

 
Romario Dominic
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.

Thanks
 
Ulf Dittmer
Rancher
Posts: 42970
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.

For something more involved, check out this article.
 
Romario Dominic
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks.I did o through the examples.In regular WebService applications,SOAP is commonly used as the messaging protocol right?Now is there any other protocol which is as useful?

Thanks
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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:
  • Hessian (Binary over HTTP)
  • Burlap (XML over HTTP)
  • Spring HTTP invoker
  • (tunneled) RMI
  • XML-RPC
  • Considerations when choosing a technology

    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

    REST vs. SOAP at Amazon
    The RESTful Web Column
    Playing Together Nicely: Getting REST and SOAP to Share Each Other's Toys
    Using REST with Ajax

    Axis 2.0: RESTful Web services Support
    [ March 01, 2006: Message edited by: Peer Reynders ]
     
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!