what is the advantages to use EJB to implement an application that would be exposed as a web services, if there is any ? why not using a javabeans only ? there is some case when javabean will not be sufficient ?
My 2 cents .. One of the primary reasons to use EJBs in webservices is, if you have a service available that is implemented using EJBs (say like a StockQuoteBean), if you need to expose this EJB to outside customers, you can expose the Bean as a WebService.
If you are planning for transactions using webservices like a OrderManagement system or TicketReservation, then you need the container benefits like Transaction/Security, then EJBs are a natural choice.
Or if you prefer the lighter frameworks, Spring will do the job for you. --pradeeP
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