the action will be
small.
David
From: Rick Reumann <[EMAIL PROTECTED]>
Reply-To: Rick Reumann <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: Re: Struts design: All actions in one ActionClass
Date: Wed, 11 Dec 2002 15:51:37 -0500
> Well, I guess I'll have to look into the "DispatchAction" thing. I've not
heard of it before today.
> It sounds real similar to what we're doing.
Also see "LookupDispatchAction" which works great if you have one form with
several different actions that could happen depending on which button the
3:29 PM
> To: Struts Users Mailing List
> Subject: Re[2]: Struts design: All actions in one ActionClass
>
>
> On Wednesday, December 11, 2002, 4:16:31 PM, Rob wrote:
>
> RL> One of the developers that took over the project merged a
> number of the
> RL&
On Wednesday, December 11, 2002, 4:16:31 PM, Rob wrote:
RL> One of the developers that took over the project merged a number of the
RL> actions
RL> edit, delete, create, list into one big ugly mess.
Was this all being done a 'normal' action class or a
DispatchAction class? I think a Dis
From: "Jordan Thomas" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts-User" <[EMAIL PROTECTED]>
Subject: Struts design: All actions in one ActionClass
Date: Wed, 11 Dec 2002 19:05:36 +0100
Hi,
What is the best
ere do I go next.
Greg
> -Original Message-
> From: David Graham [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 2:09 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Struts design: All actions in one ActionClass
>
>
> I apply this theory to jsps as well.
On Wednesday, December 11, 2002, 1:05:36 PM, Jordan wrote:
JT> a) Put all my actions for a particluar area (i.e. creating, editing and
JT> deleting user accounts) in one Action class
I guess I am in the minority here but lately I've been building
one big DispatchAction class that acts a
s" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: RE: Struts design: All actions in one ActionClass
Date: Wed, 11 Dec 2002 20:43:51 +0100
Does this also count for the J
sers Mailing List" <[EMAIL PROTECTED]>
>To: "Struts-User" <[EMAIL PROTECTED]>
>Subject: Struts design: All actions in one ActionClass
>Date: Wed, 11 Dec 2002 19:05:36 +0100
>
>Hi,
>
>What is the best way to design my application? Is it better to
gt;From: Ron Day [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, December 11, 2002 1:01 PM
>To: Struts Users Mailing List
>Subject: RE: Struts design: All actions in one ActionClass
>
>
>where do you do your business logic ?
>
>-Original Message-
>From: Chappel
where do you do your business logic ?
-Original Message-
From: Chappell, Simon P [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 12:52 PM
To: Struts Users Mailing List
Subject: RE: Struts design: All actions in one ActionClass
Abolutely go with option B. We did this and
n Thomas [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, December 11, 2002 12:06 PM
>To: Struts-User
>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 particl
TECTED]>
To: "Struts-User" <[EMAIL PROTECTED]>
Subject: Struts design: All actions in one ActionClass
Date: Wed, 11 Dec 2002 19:05:36 +0100
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
dele
"Struts-User" <[EMAIL PROTECTED]>
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,
> -Original Message-
> From: Jordan Thomas [mailto:[EMAIL PROTECTED]]
> 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 ac
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 partic
16 matches
Mail list logo
