I believe the best path for you on this is to SubClass the RequestProcessor rather than chaining. You could then use any number of different design patterns to dispatch your actions and share data between them or leverage the Workflow Extensions/State Engine.
Michael Oliver AppsAsPeers LLC 7391 S. Bullrider Ave. Tucson, AZ 85747 Phone:(520)574-1150 Fax:(520)844-1036 -----Original Message----- From: Souravmay Das [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 5:14 AM To: [EMAIL PROTECTED] Subject: how to call more than one Struts Action for a given HTTP request Hi All, I have a question can we call more than one Struts action for a HTTP Request. Do you have any idea how to do it. The basic idea of having more than one Struts actions, is for getting more fine grained reusable component. With regards, Sourav Das -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
