[
https://issues.apache.org/struts/browse/WW-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41810
]
James Holmes commented on WW-2105:
----------------------------------
I think I spoke to soon. I am seeing an issue now with the
PortletActionRedirectResult.
Here is the scenario. I have a page that has a form on it. I submit the page to
an action that adds a record to the database. The action's success result uses
PortletActionRedirectResult to redirect back to the original page that the form
was on. This all works great. The problem is that when the original page comes
up after processing the action and adding the record to the databse, the form
is repopulated with the original values. In standalone Web app mode this
doesn't occur because I believe a true new request is being made.
I believe this might be able to be resolved by creating a new action instance
in the PortletActionRedirectResult instead of using the original one. This
issue might be a symptom of the fact that I am using one action class for
displaying the page and for adding, updating, deleting. I simply use different
methods for the different behaviors. Does that make sense?
Any ideas?
> Handle redirectAction result type in a portlet
> ----------------------------------------------
>
> Key: WW-2105
> URL: https://issues.apache.org/struts/browse/WW-2105
> Project: Struts 2
> Issue Type: Improvement
> Components: Portlet Integration
> Reporter: Nils-Helge Garli
> Assignee: Nils-Helge Garli
> Fix For: 2.1.0
>
>
> To ease migration of existing web application that use the redirect action
> result type, this result type should point to PortletResult when running in a
> portlet environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
