[
https://issues.apache.org/struts/browse/STR-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41377
]
Paul Benedict commented on STR-286:
-----------------------------------
I prefer a different solution. I think it is on the wrong end of the problem to
tell configure an action on how to populate. Instead, like Struts 2, it should
be on the other end -- as a result. Thus I think a different type of
forward-like-element could exist, or another attribute:
<forward name="x" path="/file.jsp" chain="true" />
or
<chain name="x" path="/file.jsp" />
This is more flexible because then I can create chains, or not, in multiple
forwards.
> Multiple calls to populate ActionForm
> -------------------------------------
>
> Key: STR-286
> URL: https://issues.apache.org/struts/browse/STR-286
> Project: Struts 1
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0 Final
> Environment: Operating System: All
> Platform: Other
> Reporter: aria.kiahaschemi
> Assignee: Michael Jouravlev
> Fix For: 1.4.0
>
>
> Within a sequence of Actions (with no intermediate user interaction), the
> ActionForm is populated with the request parameters' values each time the
> request is forwarded to the next Action. As a consequence, an Action B,
> following an Action A, will not 'see' the ActionForm in the state Action A
> left
> it in, but instead get as the ActionForm's properties' values, the
> parameters'
> values provided with the HTTP request. (I.e. Action B 'sees' in the
> ActionForm
> what, e.g., the user entered, instead of what Action A already did with it.)
> Suggestion to discuss:
> It might be cofigurable within the struts-config.xml to set an Action to
> either 'ActionForm_population_required' (default),
> or 'ActionForm_do_not_populate'.
> Thank you in advance for any response!
> Aria
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
