Well im in the camp of "never show a jsp if you can get away with it" so almost everything in the app is fronted by an action.
Now lets say I have a class that gets a bunch of stuff out of a db, caches it, etc for dropdowns or whatever. And let's further suppose that the page (or tile) I want to show is needing these dropdowns, but its really an "entrance" page to the workflow so I really don't need to do anything in my action (other than potentially set up the dropdown stuff which would mostly be something like static calls on my class) Wouldn't it be better to just use ForwardAction with a configurable setup item class? Yes, I can do it in an action I write, but now I have 2 classes to maintain instead of one. Al -----Original Message----- From: Shey Rab Pawo [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 09, 2005 12:56 PM To: Struts Users Mailing List; Ben Taylor Subject: Re: Eliminate Setup Actions 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
