[
https://issues.apache.org/struts/browse/STR-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40325
]
Hubert Rabago commented on STR-3009:
------------------------------------
(Fixed typo)
If I created and returned an ActionRedirect from my action:
return new ActionRedirect(mapping.findForward("success")
.addParameter("foo", bar)
.addParameter("baz", bat)
...then I'm specifying at that point that I'm doing a redirect.
The redirect behavior of ActionForward was intended to be configurable, but not
the redirect behavior of ActionRedirect.
The change has only been around for one GA release (1.3.5), so it shouldn't be
that big a deal if we decide that it's a bug and revert to the original
behavior.
> ActionRedirect from ForwardConfig not redirecting properly?
> -----------------------------------------------------------
>
> Key: STR-3009
> URL: https://issues.apache.org/struts/browse/STR-3009
> Project: Struts 1
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.3.5, 1.3.6
> Reporter: Jason Millard
>
> While migrating from Struts 1.2.9 to Struts 1.3.5, I noticed ActionRedirect
> was no longer redirecting as expected.
> In the Struts 1.2.9, in
> public ActionRedirect(ForwardConfig baseConfig)
> setRedirect was always being set to TRUE, like it is in every other
> constructor.
> However, as of Struts 1.3.5 it is now being configured as
> setRedirect(baseConfig.getRedirect());
> This seems to defeat the purpose of a ActionRedirect if you are trying to
> generate one from a
> mapping.findForward();
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
