In our base action classes we have elected not to implement the execute method making them abstract actions instead. this way you can include protected methods in these classes to do validation and call them when needed. implementing exeucte method in base class seems too limiting. you could call super.execute() in your execute method but this is sloppy in my opinion. I would rather have a abstract super class.
-----Original Message----- From: Joao Batistella [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 3:02 PM To: 'Struts Users Mailing List' Subject: RE: One Action class but more than one functionality That's right. But I have a problem. I have a superclass that all other actions extend and this class only implement execute method with generic validations and so on. So, I need the execute method being called, understand? Thanks. -----Original Message----- From: Prabhat Kumar (IT) [mailto:[EMAIL PROTECTED] Sent: terça-feira, 30 de março de 2004 17:33 To: Struts Users Mailing List Subject: RE: One Action class but more than one functionality 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
