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

2004-04-23 Thread Robert Taylor
- > 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

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

2004-04-23 Thread Takhar, Sandeep
, 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

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

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

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

2004-04-22 Thread Erez Efrati
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&

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

2004-04-22 Thread Robert Taylor
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 >

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

2004-04-22 Thread Martin Cooper
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

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

2004-04-22 Thread Irfandhy Franciscus
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

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

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

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 Us