Hi Joao, technically it is no problem to use one action for multiple tasks. You can use a request attribute to determine which use case you want to work through.
But on the other side it appears cleaner to have a single action for a single use case. In our projects, we try to have separate actions for each use case. But sometimes we also share a action for use cases which are similar, like in your example. Regards, Bernhard -----Ursprüngliche Nachricht----- Von: João Paulo Batistella [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 14. Januar 2003 14:36 An: [EMAIL PROTECTED] Betreff: Design of action classes Hi. We are deciding about how to use action classes in our project. Is it a problem to let developers use the same action class to handle different operations? Example: The action UpdateUserAction could be used to insert a new user or to update the data of an existing user. Is it a problem? Or it's better to have InsertUserAction and SaveUserAction. They do almost the same thing so I think they could be same. Thanks, Joao Paulo. --------------------------------- Busca Yahoo! O melhor lugar para encontrar tudo o que você procura na Internet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
