nt: Tuesday, July 23, 2002 11:40 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Design Advice: Using DispatchAction
>
>
> Subject: Re: Design Advice: Using DispatchAction
> From: "Vic C." <[EMAIL PROTECTED]>
> ===
> Robert Taylor wrote:
> "The problem I
Subject: Re: Design Advice: Using DispatchAction
From: "Vic C." <[EMAIL PROTECTED]>
===
Robert Taylor wrote:
"The problem I am running into is that pre-processing
requirements vary within the common event groupings. For example,
let's say eventGroupA handles events 1, 2
to certain events handled by a single DispatchAction.
robert
> -Original Message-
> From: Hoang, Hai [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 23, 2002 10:07 AM
> To: 'Struts Users Mailing List'
> Subject: RE: Design Advice: Using DispatchAction
>
&
EMAIL PROTECTED]]
Sent: Tuesday, July 23, 2002 8:46 AM
To: [EMAIL PROTECTED]
Subject: Design Advice: Using DispatchAction
I'll try to keep this as short as possible.
Background:
I have various groupings of common events in my web app where
I would like each grouping of common events handled b
I'll try to keep this as short as possible.
Background:
I have various groupings of common events in my web app where
I would like each grouping of common events handled by a single
Action class. The DispatchAction class allows me to
do this. I want to do this because in my scenario,
the Action c
5 matches
Mail list logo
