dcsimg
Business Delegate / Session Facade interaction questions
3 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Mark_Perrino
Posted On:   Monday, March 29, 2004 07:48 AM

I understand the concept and the benefits of a business delegate "front-ending" a session facade. I am hoping that someone can answer the following questions: Is it acceptable if a business delegate were to front-end more than one session facade in order to create a more unified service. For example is it ok to create one business delegate that provides Account Inquiry and Maintenance functionality and behind the scenes it talks to an AccounInquiry Session Facade and AccountMaintenance Session Facade? We are looking at a designing a Account Inquiry business delegate. It will return an AccountProfile business object. A behaviour of the AccountProfile object will be update capability (i.e. update account status, modify balance   More>>

I understand the concept and the benefits of a business delegate "front-ending" a session facade. I am hoping that someone can answer the following questions:

Is it acceptable if a business delegate were to front-end more than one session facade in order to create a more unified service. For example is it ok to create one business delegate that provides Account Inquiry and Maintenance functionality and behind the scenes it talks to an AccounInquiry Session Facade and AccountMaintenance Session Facade?


We are looking at a designing a Account Inquiry business delegate. It will return an AccountProfile business object. A behaviour of the AccountProfile object will be update capability (i.e. update account status, modify balance, etc.). Considering that the business object is a "business tier" component, is it ok fif it were to talk directly to an Account Update Session Facade or instead should it use a business delegate which in turn will call the session facade?

   <<Less

Re: Business Delegate / Session Facade interaction questions

Posted By:   Anonymous  
Posted On:   Wednesday, May 12, 2004 03:01 AM

As the basic purpose of Business Delegate pattern is to decouple the controller/front end from backend. Going by this usefulness of it, its recommended to use BD to service more than one session facade. If in a application one is using only one Session facade bean, the usefulness of BD becomes limited. If one doesnot go for scalability then in that case using BD is extraneous.
My point in saying this is that if you are using BD to service only one sessionfacade you aren't taking full advantage of the BD pattern.

Re: Business Delegate / Session Facade interaction questions

Posted By:   Amir_Pashazadeh  
Posted On:   Tuesday, April 13, 2004 06:05 AM

Hi


Business Delegate is just for seperating business tier, and presentation tier.

By doing so, you extract business logic from Session EJBs and put it in classes which roles are just as an layer between two tiers.

Re: Business Delegate / Session Facade interaction questions

Posted By:   Christopher_Koenigsberg  
Posted On:   Monday, March 29, 2004 10:09 AM

I think the point of separating them is to do precisely what you are talking about -- concentrate on (aggregated) business issues in the business delegate, and concentrate on individual session issues in the session facade.

About | Sitemap | Contact