I'd say you were enforcing the pattern. The controller is the filling in the sandwhich. It can be bound to model and bound to view. By using the Action class you have the appropriate degree of seperation between the view and model (using MVC/Layers).
I'd also say that the form-beans are controller objects. The tags are the view components. The controller should be creating the ActionForm bean, handing them to the JSPs, and then reconstituting it on the next request. There is a correlation between the JSP tags and the ActionForms, but IMHO they are on different layers. -T. DHS Struts wrote: > > So when I have an entity object (model) and I wish to move data from it to > my form-bean (view), and I do so via my action class (controller) aren't I > breaking this paradigm? > > I am moving data from the entity to the form with no separating layer, other > than the activity being located within an action class. > > Is this worth worrying about, or is this just semantics? > > >From: Ted Husted <[EMAIL PROTECTED]> > >To: Struts Users Mailing List <[EMAIL PROTECTED]> > >Subject: Re: Application State == View or Business Logic > >Date: Wed, 15 May 2002 12:44:15 -0400 > > > >The Model represents application state. The View displays the > >application state. The Controller captures user gestures and selects the > >View. > > > >In a conventional "desktop" MVC application, the View may connect to the > >Model in order to display the state in "real-time". > > > >In remote applications, including Web applications, MVC is usually > >moderated by the Layers pattern, so that the View and the Controller > >interact and the Controller and Model interact, but the View and Model > >do not interact. > > > >V <-> C <-> M <-> (persistent store) > > > > > >-- Ted Husted, Husted dot Com, Fairport NY US > >-- Developing Java Web Applications with Struts > >-- Tel: +1 585 737-3463 > >-- Web: http://husted.com/about/services > > > > > >Graham Lounder wrote: > > > > > > Hi all, > > > > > > I'm starting to rethink my current code structure. One of the question > >I came up with is where the application state is supposed to be. Currently > >I have a bean which holds my state in the session. If I moved this > >application to a new client, the state bean could end up in the database. > >So my question is what is appllication state considered, model, view or > >controller? > > > > > > My guess would be model, and that you just save it in the session > >instead of the database because it is faster for web applications. > > > > > > Any ideas? > > > > > > Graham > > > >-- > >To unsubscribe, e-mail: > ><mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: > ><mailto:[EMAIL PROTECTED]> > > _________________________________________________________________ > MSN Photos is the easiest way to share and print your photos: > http://photos.msn.com/support/worldwide.aspx -- Ted Husted, Husted dot Com, Fairport NY US -- Developing Java Web Applications with Struts -- Tel: +1 585 737-3463 -- Web: http://husted.com/about/services -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
