On Wed, 9 Mar 2005 14:07:04 -0500 (EST), Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > But do you see the point in setup functions *outside* an Action's code > that occurs on the forward-level? Meaning, once an Action returns a > forward, do some setup based on what forward was returned?
Yes. I do, I think, depending on what "that occurs on the foward-level" means. If there is a generic setup tied to a forward, I would write a setup class with a setup method that returns the ActionForward that is relevant and leave all other complications out of the picture. I don't understand the point of the complications. This seems to be a regular sort of thing that does not need the complications to me. > maybe there is setup that you > want to perform regardless of which forward is returned by the Action... > yes, it happens before the Action is executed, but it hardly matters > whether it happens before or after execute() is called, as long as it > happens regardles of the forward returned is the pertinent point). I would then just write a class that does the setup and whenever that logic is needed use the class. I just don't see why this is not all easy given the present code and wonder why more is needed. I don't see the need for the extra complications. What is the problem? -- 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]
