[TRINIDAD-2048] ComponentUtils.getScopedIdForComponent() is not producing consistent scoped IDs for components relocated during tag execution

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.14-plugins
• Fix Version/s: 1.2.15-core
• Assignee: Max Starets
• Reporter: Max Starets
• Created: 02/Mar/11 21:43
• Updated: 16/Jul/12 16:54
• Resolved: 14/Mar/11 15:48

Description

getScopedIdForComponent() simply walks the parent hierarchy to append naming container IDs. However, we have components that get relocated during tag execution, so their naming container hierarchy is different at tag execution time vs. the rest of the lifecycle. To solve this problem, we need to have getScopedIdForComponent return a scoped Id reflecting the original naming container hierarchy for the component, i.e. return its pre-relocation scoped ID.

This will require API additions on UIXComponent to allow relocated components to provide their logical (original parent).