-
> From: Takhar, Sandeep [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 23, 2004 7:22 AM
> To: Struts Users Mailing List
> Subject: RE: Advantages/Disadvantages of One Action for each Use Case
>
>
> Do you use subclasses for common methods or do you use helper cla
, April 22, 2004 1:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Advantages/Disadvantages of One Action for each Use Case
>
>
> There are some major advantages to the first option, especially when you're
> building a large and/or highly customisable application. A couple of
he new thead by replying
from other thread, I forgot to delete the other thread.
It's been deleted now.
cheers,
~dion~
-Original Message-
From: Martin Cooper [mailto:[EMAIL PROTECTED]
Sent: Friday, April 23, 2004 1:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Advantages/Disadvantages of
put in the following
tag ?
Erez
-Original Message-
From: Robert Taylor [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 22, 2004 9:54 PM
To: Struts Users Mailing List
Subject: RE: Advantages/Disadvantages of One Action for each Use Case
+1.
I've been down the "option 2&
22, 2004 1:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Advantages/Disadvantages of One Action for each Use Case
>
>
> There are some major advantages to the first option, especially when you're
> building a large and/or highly customisable application. A couple of
>
There are some major advantages to the first option, especially when you're
building a large and/or highly customisable application. A couple of
examples:
* It is much easier to reconfigure your application. without needing to
change any Java code. You may think you know which "actions" are relate
cons of each one?
~Dion~
-Original Message-
From: Ravi Kulkarni [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 22, 2004 1:15 PM
To: Struts Users Mailing List
Subject: RE: Advantages/Disadvantages of One Action for each Use Case
DispatchAction is what exactly is meant for these kinds o
> Subject: Advantages/Disadvantages of One Action for each Use Case
>
>
> Hi,
>
> I was wondering what's the advantage and disadvantage of
> creating one Action for each use case, i.e. creating
> NewAccountAction.java
> EditAccountAction.java
> or even with NewAccountFormA
DispatchAction is what exactly is meant for these kinds of situations.
Kulkarni.
> -Original Message-
> From: Dionisius Purba [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 22, 2004 10:43 AM
> To: 'Struts Users Mailing List'
> Subject: Advantages/Disadvantag
Hi,
I was wondering what's the advantage and disadvantage of
creating one Action for each use case, i.e. creating
NewAccountAction.java
EditAccountAction.java
or even with NewAccountFormAction.java
vs
AccountAction.java
and inside the AccountAction we can check parameter from the JSP
then execut
10 matches
Mail list logo
