[MYFACES-580] tree2: tree component can cause duplicate id problems

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.1.1
• Fix Version/s: 1.1.1
• Assignee: Sean Schofield
• Reporter: Mathias Werlitz
• Created: 19/Sep/05 21:07
• Updated: 17/Apr/06 20:52
• Resolved: 24/Sep/05 11:18

Description

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.