[ http://issues.apache.org/jira/browse/MYFACES-580?page=all ]
Mathias Werlitz updated MYFACES-580:
------------------------------------
Attachment: tree2_duplicateIDv2.diff
updated the patch - now it does not create warnings about automatic ids
> tree2: tree component can cause duplicate id problems
> -----------------------------------------------------
>
> Key: MYFACES-580
> URL: http://issues.apache.org/jira/browse/MYFACES-580
> Project: MyFaces
> Type: Bug
> Components: Tomahawk
> Versions: Nightly Build
> Reporter: Mathias Werlitz
> Priority: Blocker
> Attachments: tree2_duplicateID.txt, tree2_duplicateIDv2.diff
>
> The tree2 renderer can cause duplicate id problems. The result is similar/
> identical to MYFACES-35.
> It seems that calling context.getViewRoot().createUniqueId() in the renderer
> messes up the component tree.
> Component tags in the jsp page within the tree or after it call internally
> UIComponentTag.findComponent().
> In this method the component of the parent tag is resolved ... somehow code
> is influenced by the call of context.getViewRoot().createUniqueId() in the
> treerenderer. While testing I found out that in case of the duplicate id
> problem, the resolved parent component for the tag is the same component (but
> not the same instance!) that is created with the processed component tag.
> I created a patch, that makes the call to
> context.getViewRoot().createUniqueId() in the HTMLTreeRenderer obsolete, but
> it might be a general issue that calling
> context.getViewRoot().createUniqueId() within the lifecycle may corrupt the
> component tree.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
