Reduces Coupling, Improves Manageability The Business Delegate reduces coupling between the presentation tier and the business tier by hiding all business-tier implementation details. It is easier to manage changes because they are centralized in one place, the Business Delegate.
This is why BD is so important.
Jacek
SCEA, SCWCD, SCJP, OCA AS10g
Sam Gehouse
Ranch Hand
Joined: Jul 21, 2003
Posts: 281
posted
0
I agree with you and fully understand the benefit of Business delegate.
I should have asked the question differently. My question is:
As two separate applications are deployed (one web, another Swing) with both using the same SLSB and DAO; I think I do not have to use Business Delegate.
Any input?
Jacek Ostrowski
Greenhorn
Joined: Feb 09, 2007
Posts: 23
posted
0
It doesn't matter how many apps you have. For some apps BD is useful, for others is not.
Here I would use BD to reduce coupling between tiers and I would share BD between both apps.
Originally posted by Francesco Bianchi: Does it means that the BD and the Service Locator are a part of the Java Application client?
Nope , they ain't part of either the app client/web client or the business app.
BD is the point of seperation of Client and the enterprise/biz app. BD completely abstracts the app client of any of the biz app changes. BD is the one that would undergo changes if Business interface changes.
SL just implements a lookup mechanism for remote objects.
So, these are not part of the app client as they can serve any of the Client applications.
As I understand, Business Delegate is like interface, which expose the "contract", the face of functionality. And the change of implementation doesn't impact (very much) BD.
In other word, Business Delegate is the front part of component. Is that right? [ May 10, 2007: Message edited by: Pham Huy Anh ]