App controller & diffr client types 2004-01-30 - By Bruce Bailey
Back
I have a question regarding some reading I have been doing in "Core J2EE
Patterns" and thought this group might be a good place to start.
I am looking at the app-controller pattern and I'm wondering about it's
application in both a web app (web clients) as well as for Java clients. The
book suggests front-ending this with a Front Controller as a way to provide
centralized access for web clients. My question has to do with whether this
pattern is appropriate for Java application clients (e.g., swing) as well,
and if so, what construct should be used (e.g., instead of a Front
Controller/servlet) to act as an interface between the clients and the App
Controller?
Or, given that my plan in the case of the web app is to invoke business
delegate(s) (in my case a POJO which will use a service locator to access
EJBs) via command objects [GoF], would it make more sense for my java
application clients to access the business delegate(s) directly? Are there
any gains in trying to maintain the app-controller pattern for java clients,
and if so, what "glue" should I use between these clients and
app-controller?
Thanks -
====================================================================
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)
|
|
