Hi Jason- The whole struts cycle starts out when the ActionServlet receives a request. It in turn determines (based on the struts-config.xml action mappings) which action class and action form are responsible for handling the request. The action class processes the request via invoking a business object (the model) and providing it with the information from the action form. The action evaluates the returned value from the business object and then alters the values in the form bean and forwards the request on. The forward destination could be another struts action or a JSP page.
So, it is right to think that things start at the Action and end at the JSP. jk > -----Original Message----- > From: Jason Vinson [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 14, 2003 7:46 AM > To: [EMAIL PROTECTED] > Subject: Struts Design (best practices) > > > Hi Folks, > > I have been working with Struts for about a week now, and I > have a few design questions. I guess the most important is the > proper flow of information and processing. When I began to code > pages in Struts, I would link to the actual jsp page, then check > it's ActionForm, then go to the Action class. Now I am beginning > to think that the proper flow is to go to the Action class, then > the ActionForm, then to the jsp. Is this correct? > > Jason > > --------------------------------------------------------------------- > 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]
