The usual solution would be to design your forms to contain hidden
fields that tell the Action which operation to perform with the next
request. So typically, there would be one button with a hidden field
that conveyed whether this was the "FirstAction" or the "SecondAction".
These would all go back to a single Action that either performed all the
operations, or forwarded onto another Action.
If you will be using this button that much, you might also consider
writing your own custom tag so the button could program itself from the
request. In general, the request is meant to convey information to the
presentation layer about how it is suppose to write itself.
In my own projects, I am experimenting with ways to make the current
ActionMappings available to the JSP, as they are to perform() and
validate(), which starts to open several doors.
[EMAIL PROTECTED] wrote:
>
> Thanks, at least it's a working work-around. But the ugly thing is, that in
> both cases the same action is called and I am forced to call the "real"
> action
> from the first action depending on the pushed button.
>
> + Action inserts "fire" bean into rquest context
> + Forward to JSP
> + JSP checks to see if fire==first. If so, write TheFirstAction button
> + JSP checks to see if fire==second. If so, write TheSecondActon button
> + submit "fires" action
> + action does nothing and forwards to the "real" action depending on the
> button.
>
> In my real world the page will be reused at least 5 or six times. So rather
> than
> putting the "Control" part of MVC in the struts-config.xml I start
> piggypacking info
> in the request and analysing this in the dummy action.
>
> However again thanks.
> Peter
