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.
I have a requirement that the application interacts with external web service.User interacts with the application to search and add certain items (obtained from the webservice).My questions are :
1).whether stateless or stateful session bean can be used in this scenario.
2).What design pattern can be used to interact with the webservice.
well you have to ask some questions, like:
- what sort of session beans can talk to web services?
- do you want to call web services direct from the session bean?
- do you want the conversation with the client to have state?
- what's the impact on the non functional requirements of each type of bean?
as for the pattern you use, you need to look at the pattern catalogue and see if any would be a sensible fit and would make the design better in terms of maintainability, scalability, performance, extensibility, reliability, etc. I would think that DAO, MVC, and Front Controller would be in there somewhere....