I think Cade's component diagram is likely a good place to start. Although I was, and continue to be, quite unsure of what I seeing in them.
The strangest thing about Cade's diagram in my mind was that he had the JSPs dependent on the 'Order Controller'. I interpreted this controller to be a Front Controller - but thought this was strange since the
JSP were dependent on it. The Front Controller pattern, as depicted in sequence and class diagrams in the various
J2EE pattern books, should have the opposite relationship to this. That is the control is the first to receive request and it delegates them (usually intermediary classes) to various other classes including the JSPs (aka Views).
So I tried to come up with an interpretation of Cade's compnoent diagrams that would allow for that I said above. What I decided was that the links in Cade's component diagrams running from the views to the controler represent an indirect dependency 'through' the user. What I mean is, the JSP render pages that the users acts on cause HTTP requests to be forwarded to the control - in this sense the JSP pages are indirectly invoking the controler.
I'd loved to know what others think about this. I've asked before but didn't hear a peep from anyone...
