look at the org.apache.struts.actions.DispatchAction class. It is exactly for the use case you described.
-----Original Message----- From: Joao Batistella [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 11:28 AM To: 'Struts Users Mailing List' Subject: One Action class but more than one functionality Hello. I have an action class to create, edit and remove a Person, for example. Is this a poor decision? I mean, should I create 3 action classes, one for create, another for edit and another one for remove? Does struts have a mechanism to help me in that? Thanks all. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
