This will work as well indeed, and is a lot simpler than what I suggested.
However it will go through the web server layers again before it gets to the
container and then the ActionServlet, which will do the usual things as with
any request. The solution I proposed was more an optimized solution and
should be considered only if performance is an issue. We actually developped
this solution as part of a DispatcherAction, which we use in forms so that
the submit can forward to more than one action (using a parameter which
contains the action path preceded by a special prefix).
Fr.
-----Original Message-----
From: Oleg V Alexeev [mailto:[EMAIL PROTECTED]]
Sent: 27 June 2001 14:39
To: [EMAIL PROTECTED]
Subject: Re: Delegating the request processing to an Action class
Hello ssuku,
Wednesday, June 27, 2001, 4:24:58 PM, you wrote:
shhc> Hi,
shhc> How can a request processing be delegated from an Action class
to
shhc> another?
shhc> Thanks
shhc> Sandhya
Return forward to another action -
return new ActionForward( "someaction.do" );
--
Best regards,
Oleg mailto:[EMAIL PROTECTED]
************************************************************************
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, you must not read, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.
http://www.capco.com
***********************************************************************
