[
https://issues.apache.org/jira/browse/TRINIDAD-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887565#action_12887565
]
Gabrielle Crawford commented on TRINIDAD-1849:
----------------------------------------------
There's a related spec issue for this too
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=153
We work around similar issues for things like showDetail and inputs in an
iterator by special casing saving their state in a method _createState.
However submitted in a subform is really request scope, and shouldn't be saved
to the facesBean at all, instead we should save this info on a request property.
> subform in table not working
> ----------------------------
>
> Key: TRINIDAD-1849
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1849
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 2.0.0-alpha-2
> Reporter: Gabrielle Crawford
> Assignee: Gabrielle Crawford
>
> The subform is setting a value on its facesBean to determine if it's the
> submitted subform.
> See org.apache.myfaces.trinidad.component.UIXSubform.setSubmitted()
> So when the subform is stamped, the value of the last row wins, since that's
> the final value saved to the facesBean. That means if you submit the last row
> everything is considered submitted, if you submit from other rows nothing is
> saved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
