struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrice" <ppich...@nerim.net>
Subject Re: Struts design: All actions in one ActionClass
Date Wed, 11 Dec 2002 18:28:56 GMT
For me, it's easy to maintain seperate actions.
If you want to group different actions in one Action class, you might use a
DispatchAction with a method for each process.

Hope it helps

Patrice

----- Original Message -----
From: "Jordan Thomas" <jot@ipa.fraunhofer.de>
To: "Struts-User" <struts-user@jakarta.apache.org>
Sent: Wednesday, December 11, 2002 7:05 PM
Subject: Struts design: All actions in one ActionClass


> Hi,
>
> What is the best way to design my application? Is it better to
>
> a) Put all my actions for a particluar area (i.e. creating, editing and
> deleting user accounts) in one Action class
>
> or
>
> b) Use a seperate action class for every action in my application
>
> or
>
> c) Put all of the actions for a particular workflow in a single Action
> class.
>
> I am looking to have an application that is easy to maintain and flexible.
> Suggestions/Advice would be most appreciated.
>
> thanks
>
> Jordan
>
>
> --
> To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>


Mime
View raw message