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. 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'. I think the easiest solution will be defining a navigation object into the session, where I may store the return path of the last action thanks, -- TREMALNAIK --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
