Hi ranchers,
working on part II and designing the presentaion-tier (a MVC2 approach) and the entry point to the business-tier I came up with the following design:
View (
JSP) -> FrontController
Servlet / DispatcherView -> ActionCommand -> BusinessDelegate -> SessionFacade...
The DispatcherView supports the FrontController by finding the appropriate newx View. Therefore the DisptcherView does all the view-management and navigation as stated in the core
J2EE patterns catalog. The ActionCommand executes business-logic which is accessed through a BusinessDelegate of the business-tier.
Looking at the core J2EE patterns, they use a ViewHelper. Now I don't really have a clear understanding of what this ViewHelper does or is supposed to do I just can't find a clear definition of ViewHelper.
Is my approach from above valid or do I need a ViewHelper (whatever it does in the end)?
Further, I plan on having a couple of component diagrams to illustrate the different components that fullfill the requirements. Obviously all the diagrams will have the MVC2 approach from above. I am now wondering if I should clutter my diagrams with always the same MVC2 or is it legal to have another component diagram that shows MVC2 apporach in detail and in the business component diagrams just have one component "presentation" and take it from there into the BusinessDelegate?
And finally, do I need a somehow detailed MVC design for the Swing Client as well, or is it good enough to show it as a single component in the business component diagrams?
Any comment is appreciated!
D.
[ August 23, 2005: Message edited by: David Follow ]