Business Delegate vs. Session Facade 2004-01-09 - By Ian Vellosa
Back
The session facade pattern is used have one clear interface into your
application. Behind that you can hide how it is actually implemented, session
beans here and there, the odd ejb, dao too etc. You can then change about the
implementation without changing your clients view of the application.
The business delegate is used to hide the fact that you have a session bean
there. It can cache the EJB look ups saving you time, and be used to convert
nasty EJB exceptions into something more user friendly. When you change your
application model from session beans to the next fade you wont have to change
your clients there.
We use both patterns, a Session Facade for a common interface, then Business
delegates to hide we have session beans there. Makes the client code really
simple.
Does this help?
regards
IV
> from: BRodr <bira@(protected)>
> date: Fri, 09 Jan 2004 14:30:38
> to: J2EEPATTERNS-INTEREST@(protected)
> subject: Re: Business Delegate vs. Session Facade
>
> Hi, all,
>
> I?ve studied both Business Delegate and Session Facade patterns, but I?ve
> not seen much difference between them when applying to simple J2EE
> applications.
> Someone can help me to understand it?
>
> Thanks.
>
> BRodr
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
