[ https://issues.apache.org/struts/browse/STR-286?page=com.at
lassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict resolved STR-286.
-------------------------------
Resolution: Fixed
Assignee: Paul Benedict (was: Michael Jouravlev)
Updated to distinguish between a forward, include, and
chained request.
> ActionForm populate strategy
> ----------------------------
>
> Key: STR-286
> URL: https
://issues.apache.org/struts/browse/STR-286
> Project: Struts 1
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.0.0
> Environment: Operating System: All
> Platform: Other
> Reporter: aria.kiahaschemi
> Assignee: Paul Benedict
> 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.
|
