The application service could be either POJO as a helper or a Session
facade.






>From: Peter Searls <psearls@(protected)>
>Reply-To: An interest list for Sun Java Center J2EE Pattern Catalog
><J2EEPATTERNS-INTEREST@(protected)>
>To: J2EEPATTERNS-INTEREST@(protected)
>Subject: Application Service Pattern
>Date: Tue, 8 Jun 2004 11:37:59 -0600
>
>When implementing the Application Service Pattern by having the Session
>Facade call an application service to handle the coordination of business
>objects, what type of class should the application service be? Should it be
>a POJO or a Session Bean(to make fine grained transactional control easily
>available)? Is is ok to use both, POJOs when transactional control isn't
>required and Session Beans when it is?
>
>Thanks for the help.
>
>Pete
>
>====================================================================
>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)


Ashraf Galal
(416)804-8359

_________________________________________________________________
MSN Premium: Up to 11 personalized e-mail addresses and 2 months FREE*
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines

====================================================================
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)