I've been in a position to train people in MVC before, and Struts in particular, and I've used diagrams to do this... one of the things I've always done in those diagrams is shown ActionForms straddling the space between V and C, and DTOs straddling the line between C and M.
I think conceptually, and keeping in mind just the original intent of it, that that is how is should be viewed... think of ActionForms as the communications conduit between V and C, and DTOs as the conduit between C and M. They don't truly belong to any one tier. Of course, there are other usage patterns for ActionForms, and people don't always use DTOs at all (I personally have tended to pass generic Collections between C and M, although I've been moving away from that thinking gradually). So, as Michael said, this is more an academic point really... you conceivably could use ActionForms in such a way that they are pretty obviously part of one tier or another, the flexibility is yours to use and abuse :) -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Wed, August 3, 2005 1:00 pm, Michael Jouravlev said: > On 8/2/05, Kent Boogaart <[EMAIL PROTECTED]> wrote: >> I guess my question is: is the action form considered part of the model? >> If >> not, what? > > Does it really matter, what you call it? > > Officially action form is not part of the Model. Model is supposed to > reside in your own code, which you call from form/action/whatever. > > On the other hand, some developers aggregate DTOs or even real BOs > into action form. Does this make action form a part of Model? Don't > think so, it is just a container at best. > > Michael. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
