You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@struts.apache.org by Joao Batistella <jo...@ptinovacao.pt> on 2004/03/30 18:27:31 UTC

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.