Many people would suggest that using Actions in Struts would be preferrable whether or not you need to do any "setup" or any "processing" in the movement from one page to another in a website.
I think of Actions as places to organize what needs to be done (processing the request) and providing any dynamic navigation needed with the ActionForward return class. With the forward being determined in the Action, this is the ideal place to manage or to delegate management of the setup as well. Thus, I don't see any value in doing "setup" prior to coming to the action. This would be desireable, I think, only if you did not want to use the Action at all. If you are going to use the Action, this is an unnecessary complication I think. I may not understand the point, however. Certainly there seems to be a lot of interest in doing this, that is, providing "pre-action" setup. I am not sure why. This thread confuses me. I don't see the point at all. On Sat, 5 Mar 2005 08:03:04 +0000, Ben Taylor <[EMAIL PROTECTED]> wrote: > Hi, > > Can anyone tell me if there is an easy way to put information > (required to populate drop down boxes using data from a db) in to the > request, without having to write a setup Action for each page as is > done here: http://www.reumann.net/struts/lesson2/step9.do . > > Thank you for any help! -- No one ever went blind looking at the bright side of life. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
