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 if 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? Thanks