On Wed, September 7, 2005 12:44 pm, Michael Jouravlev said: > Consider "standard" for Struts pre/post actions. You have showForm.do > -> JSP -> submitForm.do -> smthElse.do. > > The preceding action for smthElse.do is submitForm.do, so calling it > does not make sense, since it would try to submit a non-existent form. > By the way, your advice would work great with Struts Dialogs, where > each dialog, that is, a web resource, is controlled by one action > only.
Yep, your right, fair point. Maybe the answer, since my other reply was talking about doing it from a base Action, is to only extend from that base Action those Actions that should be "return to-able" ;) In other words, have your showForm.do extend BaseAction, and smthElse.do extend BaseAction, but NOT submitForm.do. That way you only ever store Actions that can legitimately be returned to, and in this case if you wound up in smthElse.do and wanted to return to the previous page, meaning showForm.do, that's precisely what was last stored in session, NOT submitForm.do, as you point out would be incorrect. > 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". Exactly, hence my suggestion. :) > Michael. Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
