[
https://issues.apache.org/jira/browse/MYFACES-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3186.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.2
2.0.8
Assignee: Leonardo Uribe
Thanks for the example. I checked it and it is a problem with
UIRepeat.invokeOnComponent. It assume child client ids without index should not
be resolved, but partial state saving needs it, so any programatically added
component will not be restored. The fix is do something similar to t:dataList
does.
> ui:repeat can lose dynamically added grandchild components
> ----------------------------------------------------------
>
> Key: MYFACES-3186
> URL: https://issues.apache.org/jira/browse/MYFACES-3186
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.1.1, 2.1.2-SNAPSHOT
> Reporter: Matt Benson
> Assignee: Leonardo Uribe
> Fix For: 2.0.8, 2.1.2
>
> Attachments: MF-3186.tar.gz
>
>
> Somewhat complicated to explain... myfaces-extval, for example, can make
> changes to components by intercepting Renderer.encodeBegin(). My experience
> is this:
> I have a ui:repeat, in which I nest an h:selectOneMenu. If I add its child
> elements using a renderer interceptor approach like that of extval, these are
> lost after the view is rendered, so that the form submit fails due to the
> h:selectOneMenu having no selectItems available. Other h:selectOneMenu
> components in the tree work properly when I add children in the same way,
> thus I believe that ui:repeat is where the problem arises. I am attaching a
> project demonstrating the situation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
