[
https://issues.apache.org/jira/browse/TRINIDAD-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629888#action_12629888
]
Gabrielle Crawford commented on TRINIDAD-1223:
----------------------------------------------
Actually subforms intentionally keep their submitted value. This is in the doc
"We strongly recommend the use of a single <af:form> per page, and using
<af:subform> where you might otherwise be tempted to use multiple forms.
Multiple forms require multiple copies of page state, and user edits in forms
that aren't submitted are always lost. When a page using subforms is submitted,
page state is only written once, and all user edits are preserved."
User edits are preserved by saving the submitted value.
If you want to clear them, you need to call resetValue programatically.
> EditableValueHolder components in non-submitted subform components retain
> their submitted values
> ------------------------------------------------------------------------------------------------
>
> Key: TRINIDAD-1223
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1223
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.0.9-core, 1.2.9-core
> Reporter: Andrew Robinson
> Attachments: HelloWorld.java, test.jspx
>
>
> Subform components do not restrict the decoding of child components. As a
> result, any EditableValueHolder components within non-submitted subform
> components will have a submitted value. When the page is rendered these
> components will render their submitted values and not their current value.
> Components in non-submitted subform components should either (1) not be
> decoded or (2) should have their submitted values cleared if they implement
> EditableValueHolder
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
