On Apr 1, 2005 8:53 AM, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > Perhaps that's a politician's answer, avoid giving a real answer to a > sticky question :) but I actually feel like that fits the evidence, so > to speak. Depends on what the definition of "is" is I guess :)
OK, since we've had theological, historical, and political answers, how about a scientific one? Asking what MVC layer an ActionForm belongs is a bit like asking if H2O is a solid, liquid, or gas. :) When the Action populates it from the request, it is interpreting the user gestures, and the ActionForm is part of the Controller. When the Action populates it from the database, it represents the state of the application, and the ActionForm is part of the Model. When a JSP Tag merges the its data into the page, the ActionForm is used as a helper class that is part of the View. At some point in its lifecycle, an ActionForm is all three. Albeit, the JSP tags don't care if the bean is an ActionForm or not. Likewise, the database shouldn't care if the bean is an ActionForm or not. The only member that cares whether the bean is an ActionForm instance, is the Action. Since the ActionForm is tightly coupled to the Action, and loosely coupled everywhere else, I'd say, ipso facto, like its friend the Action, the ActionForm is a card-carrying member of the Controller layer. But the mileage in your cyclotron may differ :) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
