Is this an architect issue? The project's instructions and the architect duties listed on the Mark Cade and Simon Roberts Architect Study Guide say to you keep focus on the system's architecture, not implementation details.
Are you aware of any examples of this desgin concept implemented anywhere so I can review? Or should I just assume the business delegate is embedded in the java application and not worry about representing it in a component diagram?
Peter [ June 19, 2004: Message edited by: PETER BERGOFF ]
My concern now is that the web tier owns the business delegate object but the java app will be going directly to the app server and not through the web tier. So do I need to add another business delegate to again go on to the app server tier?
Some one replied this question with the following answer! "The entire process of accessing the FFMS web server should be performed via a Stateless EJB. That will make it easy for both types of clients to access the FFMS data.
Customer Web Client ------------------- Web Browser -> Servlet -> Business Delegate -> SSB -> DAO -> HttpConnection -> CGI/Perl FFMS Web Server
Travel Agen Client (Swing App) ------------------------------ Swing Client -> Business Delegate -> SSB -> DAO -> HttpConnection -> CGI/Perl FFMS Web Server"