DO NOT REPLY [Bug 866] - Clean Way to Add Parameters to Redirecting Forward

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=866>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=866

Clean Way to Add Parameters to Redirecting Forward





------- Additional Comments From jakartauser@yahoo.com  2004-03-19 21:27 -------
Is there still interest in adding this patch?  I know there are a few things 
that I could've done better here:

1. Add support for the 1.2 feature to save messages in session and have them 
removed upon reading, if the committers feel this is needed.
2. Remove support for specifying a bundle name with a message/error key

Also, one of the users who downloaded my patch asked for support for specifying 
a property name to be associated with each message/error key sent with the 
redirect.  The original patch puts all messages as GLOBAL_MESSAGE.

Aside from these, I made by best guess for class names, attribute names, and 
parameter names that the committers may want to change.  

Ted, did you get a chance to take a look at it?  What are the changes needed 
before it can be added?  

I can work on the changes this weekend.  I can also start working on a patch to 
support this feature on the Struts-Chain RequestProcessor.

I really think it would be helpful if this functionality is built into Struts. 
Doesn't have to be *my* patch.  Folks on the user list who need this are coming 
up with homegrown solutions and not everybody gets it right everytime.

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org