This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I think that it is possible, but whether it may be used or not due to the architecture of your application. In the architecture "Swing + EJB + Database", I strongly recommend that you don't use FrontController, it will make more complex to introduce it, I perfer to use a Proxy.
But in the architecture "Swing + web + EJB + Database", it is appropriate to use FrontController as all client request data must be translate into Stream. This FrontController will communicate with another FrontController locating web tier.
best regards [ March 24, 2005: Message edited by: Along huang ]
SCJP1.4 SCJD 2<br />SCEA(In progressing)
Joined: Sep 21, 2003
Thanks. I understood what you mean and I agree with you.
Another question: Is it meaningful that we apply "application controller" and "context object" between swing client and bussiness delegate? I think bussiness delegate is too fine grain for different clients. I wanna a more coarse grain design, such as command pattern, for swing client.
The front controller(delegates to application controller included) is a centralized place for view and action management. The view management of the swing client obviously should stay with the swing, the action management, should be still there, if you use http way to link the client and server side(ex: java web start).