Hi,
Well, i said "better" due to sake of simplicity. Keeping all the logic in
Dispactch action seems complex to me. And right now I've implemented more or
less same technique (not exactly Dispatch action) and the code is bit
complex to me. Again for JSP's, I don't want to make code complex by
putting if-else logic. But it depends how much you have to write if-else? If
it is couple of conditions and more resusability, then I would prefer it
Regarding the word "better", I would suggest don't take it serious. I
said "better" w.r.t me. This is not any claim in support of separate
actions. However, being a junior developer, I'm always looking for effecient
and recommended development approaches by senior developer's community.
Bye,
Viki.
On 12/28/05, Rick R <[EMAIL PROTECTED]> wrote:
>
> Vikrama Sanjeeva wrote:
> >
> > Having separate Actions for insert, update and delete is better.
>
> Why? Do you make separate DAO objects? ie UpdateDao, InsertDao,
> RetrieveDao? I'm guessing you don't. So, it would help if you backed up
> your claim that separate Actions are better than a Dispatch action
> instead of just claiming it's better.
>
> > Your approch for making SetUpAction is right, but it's better to make
> separate
> > JSP's instead of writing if-else logic for headers and other related
> > messages.
>
> So you would rather duplicate JSPs to make basically identical Edit and
> Insert pages except for a simple header and possibly a different button?
> Please explain how in the world that is "better."
>
> I'm hoping it's just a language barrier that is making you appear so
> dogmatic in your claims. You might choose to do things differently but
> it would help if you gave some reasons why you make such bold claims
> about things being "better."
>
> --
> Rick
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
