Typically, there would be a finite number of inputs, and you could have
a logical forward for each one.
The ActionMappings form an API for the legal entry points to the
application.
Usually, the only thing that is truly dynamic is a reference into a data
source, to look something up. In that case, the link tag can take one or
more dynamic parameters, based on the collection of beans used to write
it.
In that case, the action usually gets the parameters from the request,
and uses them to look up whatever is required.
David Corbin wrote:
>
> I'm definately talking about "forward", but my "whatever" value is dynamic.
> It's based on input (a parameter) into the action. I don't yet understand
> the best solution for that.
>
> ----- Original Message -----
> From: "Ted Husted" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, August 26, 2001 2:56 PM
> Subject: Re: Dynamic forwardings...
>
> > For a forward, you just put in an encoded query string for the path:
> >
> > <forward name="itemAdd"
> > path="/do/item/Add?code=whatever"/>
> >
> > For an action mapping, you can use the parameter property
> >
> > <action
> > path="/do/item/Add"
> > ...
> > parameter="add">
> > </action>
> >
> > and have the action check for the code there
> >
> > String code = mapping.getParameter();
> >
> >
> > David Corbin wrote:
> > >
> > > I've got a an action "add", which requires a an argument "code".
> > > One (at least) of the possible forwards needs to specify this "code" on
> the
> > > forward URL.
> > >
> > > How can I do that?
> > >
> > > Thanks
> > > David Corbin
