On 9/7/05, Tremal Naik <[EMAIL PROTECTED]> wrote: > 2005/9/7, Michael Jouravlev <[EMAIL PROTECTED]>: > > Apparently, in "standard" approach with pre/post actions it makes > > sense only to store pre-actions, that is, the rendering actions. In > > the case above it would be "showForm.do". > > well, I didn't really want to store the previous action path > (showForm.do), but instead the ActionForward path which correspond to > the one returned by the previous action.
You mean, you want to jump directly to JSP instead of action class that shows the JSP? This is usually a bad idea. It is better to use actions in front of JSPs, it this case as well. But if you know what you are doing... > So I'd have the nice effect > of don't calling the previous action (it may be a vaste of resource), > just forwarding the actual to the forward path of the previous. I can > imagine I must be careful that all the object needed by the previous > are still 'alive'. Exactly. If you objects have request scope you would need to create them in the action. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
