Thanks Michael. I'm just picking my way through your answer ... Ok, the <jsp:include> bit is interesting ... and I'm going to consume that in detail later, that's a lesser case at present. One question on the non-include side ... ->
Michael Jouravlev wrote: > On 5/3/06, Rob Manthey <[EMAIL PROTECTED]> wrote: > >> ... action knowing dynamically what jsp it's called from ... > > Unless it is the case of <jsp:include>, I personally believe that > action should not know or care to know where the request came from. I'm anticipating that this is on the back of an MVC axiom that the action updates the model and then the jsp just fetches the assets it wants from the model, so the "which assets does the action need to populate" is catered for by not anticipating which page you are heading for, just update all assets that the action has tainted. (I'm probably still missing the finer points, as this seems not to be as "lightweight" an approach as updating the assets that were tainted by the action *and* are going to be wanted in the next jsp, but ok it would solve the asset selection problem.) However (correct me please), surely *something* needs to know which jsp to fetch to return to the user ... ? If this is removed from the action's responsibility, how do I configure the Struts1 framework to dynamically route back to the right page when an action can be called from multiple jsps ... ? struts-config.xml seems to only allow one page for an action to anonymously default back to after completion ... <action input="pagename">. Your patience is appreciated. If the answer is in a nuance of your previous reply, feel free to textually slap me. Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
