I would say that the action would be the first class that the User actor
would invoke the execute method with. The next class would I suppose be the
method of a manager that you invoke from the action and then whatever
classes such as DAO's you invoke following that.
----Original Message Follows----
From: "Stuart" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
To: <user@struts.apache.org>
Subject: UML and Struts
Date: Mon, 17 Jan 2005 20:45:31 -0800
Hi,
I am creating some UML (sequence diagrams) for an application in which we
will use Struts. Does anyone have any suggestions on the best way to draw
the UML such that its clear that Struts (or at least MVC) is being used but
does not end being UML just about Struts? I guess what I am asking is what
key strut classes would you put on a UML sequence diagram to describe the
architecture of a web application when you do not want the focus to be
struts?
Thanks in advance for your help.
Regards,
Stuart
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
