To chain actions, you simply return a non-redirect ActionForward which points to a Struts action path. This is chaining (where a redirect isn't) because it results in the ActionServlet triggering a second "run" through the RequestProcessor's processing flow.
OK, that's what I was thinking, along with using the trick to set the arguments on your forwards (see http://wiki.apache.org/struts/ForwardingWithDifferentParameter)
This can have some unexpected side effects, which is one reason it's not considered "supported behavior". Also, as Ted notes on the references Wiki pages, when people chain actions, it is often (though not always) because they haven't got a clean controller architecture.
Fair enough.
I notice that the email from Craig included in that page is over two years old and heavily references the transition from Struts 1.0 to Struts 1.1; is that still useful this far on?
I don't think so.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
