I am working on sequence diagram and want to know
how to show JSP in sequence diagram.
Because it doesn't have a class name so how do I present JSP in sequence diagram?
Use a Lifeline Actor or a simple Lifeline?
The assignment requires to show JSP in component diagram. I think that means you need to have entire flow designed including the JSP page.
If there is no JSP in sequence diagram then no one calls controller. Also it's hard to know if your controller design is correct without JSP.
You certainly need to show an actor issuing commands to a front controller.
The idea of creating a wire diagram for the JSF pages is way off, in my humble opinion. The job of an application architect is not to design a user-interface, or for that matter, paint the user interface designers into a box.
The UI design should easily be put together using facelets, or JSPs, or whatever, without impacting the integrity of the designs provided by the application architect.
That's my opinion and experience. Dont' hesitate to disagree.
"you need to have entire flow designed including the JSP page"
Perhaps I'm reading too much into what you mean by 'entire flow?'
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.
What is the purpose of the Business Delegate in the EJB3.0 world? And I'd also wonder if your session bean is any different from your service class. In EJB 3.0, the service class is the session bean, because it just gets annotated. Are they two different things? If so, why?
Having thought of implementing "application service" pattern( in exam point of view), I tried to use additional layer "Business service" with session bean. I agree with you this is not right candidate in usage of patterns.
Regarding Business Delegate in ejb 3, Dependency Injection is remove the JNDI with service locator in Business delegate class.Since remote exceptions are unchecked in ejb 3, some decoupling is required between business and presentation tier. Can annotated session beans remove this tight coupling & override the responsibility of business delegate?
Can you please give more clear picture on this or share reference documents?
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop