Everyone, thank you for the response.
Martin Cooper wrote:
This sounds to me like a rather blatant mis-use of actions. In the first
place, as Michael points out, action chaining has always been an
anti-pattern in Struts.
As Michael later pointed out (and I should have explicitly said), this
is not about action chaining. I do not pass data from one action to the
next. These actions are self-sufficient in their data retrieval and
render multiple portions of a page. It just happens Michael does the
same thing and so that's how he guessed at my implicit point. Because S1
so conveniently supplies an "include" attribute on the action mapping,
it's just so easy to invoke multiple actions to render a composite page.
Bob Lee write:
> I've needed this, too. You should be able to implement it with an
> interceptor. Apply the interceptor globally to all your actions. If
> the current action has a "private" parameter, the interceptor can
> verify that it's being entered a second time (i.e., the first time was
> through a public action which chained to this private action).
Wendy pointed out my email was about Struts 1. But it's a blessing in
disguise I didn't mention the version, because I was happy (and hoping)
to see that someone else was wanting the feature.
Any further reflections?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
