I agree that Struts in Action is a good book (heck, I reviewed it: http://books.slashdot.org/article.pl?sid=02/11/25/1731249&mode=thread)
But after having a frustrating day yesterday trying to get a handle on client side validation using the 1.1 validator, someone on this list hit me to the fact that this book was written against 1.1 beta 2 and not beta 3 (which just came out), and there have been a few changes. Be sure to read the online release notes: http://jakarta.apache.org/struts/userGuide/release-notes-1.1-b3.html To pickup the changes from b2 -> b3. -----Original Message----- From: Susan Bradeen [mailto:[EMAIL PROTECTED]] Sent: Friday, February 14, 2003 8:26 AM To: Struts Users Mailing List Subject: RE: Struts Design (best practices) Hi Jason, Pick up a copy of Struts in Action. It is a good read, and it will save you a lot of "trial and error" time, figuring out how the framework works. There are a few Struts books out now, and all are extremely helpful. Good luck, and welcome to the Struts group! Susan Bradeen On 02/14/2003 07:56:17 AM Jim Krygowski wrote: > 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] > --------------------------------------------------------------------- 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]
