RE: Advantages/Disadvantages of One Action for each Use Case

2004-04-23 Thread Takhar, Sandeep
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 examples: * It is much easier to reconfigure your application

RE: Advantages/Disadvantages of One Action for each Use Case

2004-04-23 Thread Robert Taylor
: 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 classes or neither? sandeep -Original Message

Re: Advantages/Disadvantages of One Action for each Use Case

2004-04-22 Thread Irfandhy Franciscus
~ -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 of situations. Kulkarni

RE: Advantages/Disadvantages of One Action for each Use Case

2004-04-22 Thread Robert Taylor
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 examples: * It is much easier to reconfigure your application

RE: Advantages/Disadvantages of One Action for each Use Case

2004-04-22 Thread Erez Efrati
in the following tag html:form action=?? ? 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 road

Advantages/Disadvantages of One Action for each Use Case

2004-04-21 Thread Dionisius Purba
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

RE: Advantages/Disadvantages of One Action for each Use Case

2004-04-21 Thread Ravi Kulkarni
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/Disadvantages of One Action for each Use

RE: Advantages/Disadvantages of One Action for each Use Case

2004-04-21 Thread Dionisius Purba
of One Action for each Use Case 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/Disadvantages