You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2012/12/14 03:40:12 UTC
[jira] [Resolved] (MYFACES-3663) UIViewRoot.createUniqueId() should
generate unique ids for all the component tree.
[ https://issues.apache.org/jira/browse/MYFACES-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe resolved MYFACES-3663.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.11
2.0.17
> UIViewRoot.createUniqueId() should generate unique ids for all the component tree.
> ----------------------------------------------------------------------------------
>
> Key: MYFACES-3663
> URL: https://issues.apache.org/jira/browse/MYFACES-3663
> Project: MyFaces Core
> Issue Type: Bug
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.0.17, 2.1.11
>
>
> In JSF 2.2 spec there is a change related to UIViewRoot.createUniqueId(). The javadoc says this:
> "... Generate an identifier for a component. The identifier will be prefixed with UNIQUE_ID_PREFIX, and will be unique within the non-NamingContainer child sub-trees of this UIViewRoot. ..."
> Thinking in MYFACES-3660, this fact becomes more evident. I think we should not wait to 2.2 and instead implement this is 2.1.x/2.0.x branches because it will improve the stability of the component tree under dynamic addition/removal.
> The suggested solution is do something like this:
> j_id__v_1
> j_id__v_2
> j_id__v_3
> j_id__v_4
> ....
> This solution will keep ids small and will not cause any conflict with facelet created components or components that receive the ids through UniqueIdVendor/NamingContainer hierarchy:
> j_id1
> j_id2
> j_id3
> j_id4
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira