On Tue, 18 Jan 2005 17:48:08 +0000, Mark Benussi <[EMAIL PROTECTED]> wrote: > Well Jim I know you are a well respected man on this group but I would say > in defence that the JSP is not invoking it is the url of the html in a users > browser. The only place I could see a jsp living would be on the return > call.
When I think of sequence diagramming a Struts app, I think of putting the Struts request processor as the leftmost column (the HTTP request is essentially a method call into it), with columns to the right for each of the application casses that RequestProcessor calls out to (form bean, action, and the JSP or whatever resource at the end to do the rendering. Unfortunately, that means the sequence diagram for nearly every action in a Struts application will be exactly the same shape -- only the names of the invoked classes will be different. To me, that makes a sequence diagram not the most useful way to "draw" a Struts app's architecture. I think a flowchart showing the flow from each page to the action that it submits to, with outbound arrows to the pages that get rendered, conveys more about the overall structure. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
