That's exactly the way I see it, Guru. That's the extend of my "JSP" in a sequence diagram, and to be honest, I never actually use "JSP", but instead, just refer to an 'actor'. The input page being a HTML page, JSP page, facelet page if you're using JSF 2.0, or even a
servlet, isn't important, and in my opinion, might be too rigid, forcing the developer into a box. What's important is that an actor issues a command - the artifiact used to generate the UI that issues the command isn't relevant to the sequence.
JSP/JSF -->Controller-->Controller --> Business Delegate-->Session Facade-->Session Bean-->Entitty Bean
To be a
jerk and overly critical, I might even say that the JSP/JSF reference is awkward, and demonstrates how using JSP/JSF/Facelet here instead of just identifying the actor is awkward.
To be even more persnikity, I might question the use of a Business Delegate and an "Entity Bean" in a JEE5 application. Entity Beans don't really exist anymore, and the need for a business delegate has been greatly diminished with JEE5. And don't even get me started about calling the controller twice!!!
BTW, re-reading my last few posts, I'm sounding like a 'know it all.' This is just my opinion, and how I approach the issue. I could very well be wrong.
