If you do app for yourself, then I think it is for your liking. If you want to create a library, then having one method processing all commands allows you to define only one interface once and for all. On the other hand, this interace would not define the possible commands, it will be too flexible.
On 4/22/05, Marco Mistroni <[EMAIL PROTECTED]> wrote: > Hello, > In a scenario where I am using a DispatchChainAction > Where I have n methods, what could be good strategy to use > With Commons-Chain? > 1) 1 command per method > 2) 1 command for all method, where I pass a parameter > saying what I want to do? > > Anyone has any idea? > > Thanx and regards > marco > > --------------------------------------------------------------------- > 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]
