Yes, that's the general idea. Like I said, I haven't looked at it
closely yet to see if it's doable for the existing *DispatchAction
flavors. *If* it can be done (some methods just can't be moed that
easily), then the functionality becomes available to Action subclasses
that don't extend one of the DispatchAction classes.
On Thu, 16 Sep 2004 15:07:36 -0700, Michael McGrady
<[EMAIL PROTECTED]> wrote:
>
>
> Hubert Rabago wrote:
>
> > public ActionForward execute(_usual_params) {
> > RequestUtils.dispatch(this, _usual_params);
> > }
> >
> This will work fine for SimpleDispatchAction, in fact I LOVE IT and I am
> going to do it, if you don't, but this would not replace DispatchAction,
> LookupDispatchAction or MappingDispatchAction, and there probably is a
> lot of code out there with those actions. You would have to provide the
> following four options.
>
> RequestUtils.dispatch(this,_usual_params);
> RequestUtils.lookupDispatch(this,_usual_params);
> RequestUtils.mappingDispatch(this,_usual_params);
> RequestUtils.simpleDispatch(this,_usual_params);
>
> I want to emphasize, however, that
> RequestUtils.simpleDispatch(this,_usual_params) will do everything that
> the others do and do what they do more simply, but it is based on
> different data.
>
> Michael
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
