multiple action classes per use case?

[John Rothfield <jo...@sfhypnosis.com>]

I have a use case, say edit customer that has a number of steps in it.
Should I have one action class for the use case or multiple action classes,
one for each step? In the past I've used a single class in this situation
with a switch.
Anybody know the best practice?

To put it another way, I have a form with multiple submit buttons that do
different things. Should I create a new action path in struts.config and a
new action class for each button?

John



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>