This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by Alex Turcot: If I create a Web Service, would my logic be my EJBs? The web service is just another way to access my logic, right?
Technically JAX-RPC can generate endpoints that are based on either on a servlet or an EJB. However Axis only supports the servlet version; a J2EE 1.4 compliant application server has to support both. However just like (EJB) components should be at a higher granularity than objects, Web services should at a higher level of granularity than a component (hence the name "service"). Ideally you want your Web services to exchange context complete XML documents (usually referred to as a Document-oriented Web service). Simply exposing existing EJB stateless session beans is less than ideal and the currently rampant practice of using Web services for RPC really is a misapplication of the technology (considering the overhead).
Originally posted by Alex Turcot: Also, If this is true, and my fonctionalities are now accessible by web services, should my jsp+servlet access them via the web service instead of going directly to the EJBs?
No - if you plan on consuming the service internally you should expose it through an alternate interface that can be accessed more efficiently. XML marshalling can become a performance concern.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com