Gurukant Desai wrote:hmm.. Good question
I am not able to identify any particular code that should be part of Business Delegate, but it is standard practice to invoke any SLSB from presentation tier through Business Delegate, Right?
So Business Delegate will only contain method call to invoke SLSB containing business logic. Please inform if anything is wrong with this approach.
Gurukant Desai wrote:Hi Nilesh,
I dont see any scalability issue if we use "sessionfacade", which is a type of service facade. Becasue it is a session bean anyway. so its scalability will be managed by EJB container.
Details are available at http://www.corej2eepatterns.com/Patterns2ndEd/ServiceFacade.htm
Having only one SLSB which is acting as WS client is fine, but then where will you put your business logic?
I have considered two SLSBs because one SLSB will have business logic and part of Business tier, where as secong SLSB will act as WS client and will be part of Integration Tier (Separation of concerns).
And any way calling method of WS client SLSB from Business tier SLSB will not sacrifice scalability also, and is perfectly ok.
Please reply if any one see any issue with this design. Thanks!
Gurukant Desai wrote:Hi Nilessh,
Yes, I am still considering this approach.
But in Cade's book they have not shown "WS client" in any of the diagrams. Hence I am planning to adopt same approach and I will not display "SLSB2 in integration layer(WS client)" in any of my diagrams.
"SLSB2 in integration layer(WS client)" will act as a proxy class to access Webservice through JAX-WS API (SOAP Message).
But rather than acting only as proxy to SLSB2, SLSB1 in business tier will also contain actual business logic.
Please reply if anyone see any issue with this approach.
Gurukant Desai wrote:Hi Saket,
Implementing WS-Client as SLSB will improve scalability because its instance will then be maintained by container.
Gurukant Desai wrote:Thanks Nilessh for highlighting other benefits of using SLSB as WS-Client!
Saket, Please check below mentioned thread for more information.