[MYFACES-3064] UIView.createUniqueId shouldn't call encodeNameSpace to build the id.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.10, 2.0.4
• Fix Version/s: 2.0.5
• Component/s: General
• Assignee: Leonardo Uribe
• Reporter: Michael Freedman
• Created: 10/Mar/11 00:12
• Updated: 04/Apr/11 21:45
• Resolved: 11/Mar/11 00:33

Description

Submitting a new bug based on one I recently reopened as it pertains to 1.2 and 2.0 impls as well:
Referer bug: https://issues.apache.org/jira/browse/MYFACES-702

Problem reported in the above bug is related to the component's id being prefixed with the portletNamespace which is caused by calling encodeNamespace. Why is this api called in generating the component id. encodeNamespace was added to external context by and large for the portlet environment to allow it to prefix client ids to be unique on the page they are being incorporated into. Is there a reason for needing this when generating the component id? FYI ... Mojarra doesn't make this call from createUniqureId.

Hopefully, this is something that can be fixed by just removing the call ....

Issue Links

• is cloned by: MYFACES-3066 CLONE - UIView.createUniqueId shouldn't call encodeNameSpace to build the id (1.2.x branch).
• is cloned by: TOMAHAWK-1565 CLONE - UIView.createUniqueId shouldn't call encodeNameSpace to build the id. (tomahawk 2.0.x)