You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Marco Mistroni <mm...@waersystems.com> on 2005/04/22 16:16:13 UTC
RE: Struts 1.3 & DispatchAction. command question
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: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Struts 1.3 & DispatchAction. command question
Posted by Michael Jouravlev <jm...@gmail.com>.
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 <mm...@waersystems.com> 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: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org