What about allowing Action objects to add the parameters themselves? It adds a
great deal of flexibility, and doesn't limit the set of parameters that can be
used, nor does it require using the request or session attributes.
ActionForward forward = mapping.findForward("lookup");
forward.addParameter("param1","value1");
forward.addParameter("param2",2);
forward.addParameter("param3",3.0);
return forward;
Or maybe support for both (merge and addParameter).
This will also make bug 866 go away.
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> Don Brown wrote:
> > Is there one? I have several ideas I'd like to toss into the
> > discussion.
> >
> > Don
>
> There's a Whiteboard page in the Wiki.
>
> http://nagoya.apache.org/wiki/apachewiki.cgi?StrutsWhiteboard
>
> I'll be posting more about Jericho, but wanted to get what I had so far
> (a starter DTD) under CVS.
>
> One other idea that I've been meaning to bring up in the wake of
> wildcard Mappings, is the idea of merging context attributes into
> ActionForward paths. For example, we could do something like
>
> <forward name="lookup" merge="true" path="/lookup.do?key={key}" />
>
> and have it replace {key} with request.getAttribute("key") (or session
> if not found).
>
> -Ted.
>
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
