I think there's some disagreement because they kind of straddle the line. ActionForms can be simplistically thought of as Data Transfer Objects (DTO's) between the view and the controller. I say that's simplistic because of things like validation, which arguably makes them more than just DTO's, but I think it's still a reasonable simplification.
In that light, they don't truly belong to EITHER tier. Just like when you create real DTO's to pass to your model from your control layer, they don't really belong to either tier... I suppose at a given point in time you could say they belong to either or, but that's probably splitting hairs a bit. If your drawing sequence diagrams, I think you should represent them almost as their own little layer, between view and control. Or another approach might be to draw them as part of the view when sent from the view, and part of the controller when sent from the controller. I'm not sure that would lead to any LESS arguments, and perfectly valid ones on both sides, but it would at least give you a standard. :) -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Fri, October 29, 2004 1:47 pm, [EMAIL PROTECTED] said: > There seems to be some disagreement among my collegues regarding wether > actrionform is logically is part of View or the Controller in MVC, this is > relevent to us in drawing high level sequence diagrams. I personally feel > that it is a part of the view, because if a request goes to the view and > validation fails, an error message is returned to the user without > invoking any controller logic. Any opinions? Thanks.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
