This is a valid technique. I want to comment on the user experience aspect of it.
Say, that "/application.do" displays a form that a user has to fill out. He makes a mistake and you have to redisplay the form by calling "/application.do". Will the query paramter be the same? If not, then "/application.do?test=..." URLs will be building up in the navigation history of the browser. If a user made a mistake three times, you redisplayed a page three times, and all these three times the URLs are different. Then if a user wants to "unwind" back to a page that preceded "/application.do", he would have to click Back four times instead of just one. Instead of returning to previous page a user first would be returning to previous *states* of /application.do resource. If you would like to prevent above address buildup, then URLs for redirection should be *exactly* the same, in this case browser would not store duplicate addresses in the history. If you interested, read more here: http://wiki.apache.org/struts/StrutsWebIslands If you do not care about address buildup and backward navigation, then sending a parameter with redirected request is totally legitimate and simple solution. On 7/20/06, Felix Khazin <[EMAIL PROTECTED]> wrote:
I just found I can use ActionRedirect which solves all my problems: It allows me to redirect and add query string parameters!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
