I assume that you know that you can specify your ActionForward in your
Action's methods, e.g. return new ActionForward("myPage");? You can
also specify all sorts of forwards in the mapping for success,
failure, etc. Just do this instead for update, delete, etc. with the
CRUD formula. You would be better, in my opinion, to jettison the
bloat in LookupDispatchAction for one of the solutions at
www.michaelmcgrady.com, my doppleganger. ///;-)
Jack
On 5/4/05, Tom Viers <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am using a LookupDispatchAction to consolidate CRUD actions for a
> particular element in my application.
> As far a I can tell, only one input can be specified for this lookup
> action.
>
> Is there a way to dynamically specify the input forward based on which
> action method was dispatched?
>
> I have tried calling setInput() on the mapping, but an
> IllegalStateException is thrown "Configuration is frozen".
>
> Thanks in advance for the help,
> Tom
>
> Tom Viers
> PICA Programming Team
> [EMAIL PROTECTED]
> ext 2148
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
