Java Mailing List Archive

http://www.junlu.com/

Home » Home (12/2007) » J2EE Pattern »

ApplicationService can encapsulate client specific behavior? -what about SessionFacade as the only one entry point to app?

Maciek Z.ywno

2004-01-16


Hello,

I've read about ApplicationService pattern and although I generally
understand the idea behind ServiceFacade and ApplicationService
patterns, I am now a bit confused. If I properly understand
ServiceFacade, it is *only* to expose coarse-grained interface for any
type of a client, i.e. rather no logic in it. So having done an app we
tell the world: here are our ServiceFacades, go and use it. And each
type of a client may have its own specific business delegate, wright?

And now I've read that ApplicationService, which lies behind
ServiceFacade, can interact different ways for different request types
and specific clients. How is it possible? (I thought that the only
client of ApplicationService was ServiceFacade).

What am I missing? Could you give an example of such specific
ApplicationService interaction?

Thanks in advance

Maciek Zywno

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


©2008 junlu.com - Jax Systems, LLC, U.S.A.