If the managed bean need to get some data or update some data by calling the web service, then which would be best way
1. Managed bean --> Business Delegate --> Service Locator --> Stateless session bean(Session Facade)--> Calling the Web Service
2. Managed Bean--> Business Delegate (Assuming Server Side Component )--> Calling the Web Service
Is there a topic that is not discussed on this forum !
Joined: Aug 01, 2011
s patnaik wrote:
Managed bean --> Business Delegate --> Service Locator --> Stateless session bean(Session Facade)--> Calling the Web Service
I assume BD is a POJO here. The Stateless session bean that invokes the web service looks more like a DAO to me. Does it hold any other business logic as well?. I assume not(Assumption 1)
If i Use the dependency Injection i could avoid the Service Locator b/w the Business Delegate and Stateless session bean . This was brining me one another question with the data which is coming from the Webservice if I'm not changing anything or if i dont have the business logic I'm just wondering do i still need to have the Session Bean? Or Can i simply have something like this
Managed bean --> Business Delegate -->Calling the Web Service , Here my business delegate acting like converting all the remote exception to application specific exceptions and caching the results. Is this is a good approach?
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
subject: Interaction b/w Managed Bean and Web Service