This week's book giveaway is in the OCMJEA forum.
We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line!
See this thread for details.
The moose likes Web Services and the fly likes Which implementation to choose for a Web Service Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Which implementation to choose for a Web Service" Watch "Which implementation to choose for a Web Service" New topic
Author

Which implementation to choose for a Web Service

Marco Palazzini
Greenhorn

Joined: Apr 18, 2002
Posts: 13
Hello everybody
I am working to an application that has been designed as a collection of Web Services, and I am trying to understand which implementation is most suitable. I have never been developing J2EE applications but I know that a Web Service for example may be implemented as an EJB. But it may also be implemented as a Servlet as well...
I was thinking that having some examples of real implementations in mind it would have helped me.
So I am here to ask you to send me a brief description of any 'case' you have worked on.
Thank you very much,
Marco
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Generally, I would only use an EJB if one of the other requirements called for an EJB -- that is do you need method-level security, 2PC transactions or distribution. Otherwise, implementing a web services as a Plain old Java Class (called the "Java Bean" approach) often works best.
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Ravi Verma
Ranch Hand

Joined: Aug 30, 2001
Posts: 42
Hi There!!!
It sounds very intresting but i have one suggestion its like If u are using a Set of Web Services and you wanna call them go with Servlet approach and Bean will be the end processor of the Request. In any case U communicate over HTTP so the controler will be Servlet and Model will be Bean. More over the Servlet implementation for a Web Services is quite flexible and easy to implement.
Well i convenyed my Idea.. hope this will Help U


Ravi
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Which implementation to choose for a Web Service