You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2007/12/09 05:13:35 UTC

[jira] Resolved: (STR-2587) Enhancements for ActionRedirect

     [ https://issues.apache.org/struts/browse/STR-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict resolved STR-2587.
--------------------------------

    Resolution: Fixed

> Enhancements for ActionRedirect
> -------------------------------
>
>                 Key: STR-2587
>                 URL: https://issues.apache.org/struts/browse/STR-2587
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Core, Extras
>    Affects Versions: 1.2.7
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Paul Benedict
>            Assignee: Paul Benedict
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Now that Struts 1.2.7 supports the ActionRedirect class, I am constantly finding
> myself coding this pattern:
> ActionRedirect redirect = new ActionRedirect(mapping.findForward("name"));
> Something simpler would be:
> ActionRedirect redirect = mapping.findRedirect("name");
> Now someone needs to debate the merit of this approach. Should this find any
> forward and turn it into an ActionRedirect, or only find forwards that have the
> @redirect set to true. I don't know. Let's discuss.
> Also, I like to pass form attributes or request parameters from one request to
> another. How about a shortcut to populate the parameters like:
> redirect.addRequestParameters(request);
> redirect.addFormAttributes(form);

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.