This can be done by having an abstract BaseAction which extends Action and change all your actions to extend the BaseAction. This allows you to do any setup or logging for all actions.
I can send you an example if you need it. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the "Open Minded Developer Network" http://www.open-tools.org/struts-atlanta > -----Original Message----- > From: Eric Weiss [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 9:36 PM > To: [EMAIL PROTECTED] > Subject: HOWTO add actions to the Struts "pipeline" > > > I want to add an action to the Struts "pipeline" so that every single > request will cause the ActionServlet, or any other entity, to trigger a > custom service/action. > Basically I want to add one or more custom "Helpers" or "Managers" that > will perform some processing for every request and then return control to > the ActionServlet so it can process the request and forward on to the > requested ActionClass. I want these custom actions to fire for every > request and I want to fire some before the ActionClass(s) and some after > the ActionClass(s) is done. > What mechanism(s) does Struts offer that will allow me to plug into the > existing Struts pipeline? > > Thx, > Eric Weiss > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
