MyFaces Core
  1. MyFaces Core
  2. MYFACES-3064

UIView.createUniqueId shouldn't call encodeNameSpace to build the id.


    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.10, 2.0.4
    • Fix Version/s: 2.0.5
    • Component/s: General
    • Labels:


      Submitting a new bug based on one I recently reopened as it pertains to 1.2 and 2.0 impls as well:
      Referer bug:

      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


          Michael Freedman created issue -
          Leonardo Uribe made changes -
          Field Original Value New Value
          Link This issue is cloned as MYFACES-3066 [ MYFACES-3066 ]
          Leonardo Uribe made changes -
          Link This issue is cloned as MYFACES-3067 [ MYFACES-3067 ]
          Leonardo Uribe made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          Assignee Leonardo Uribe [ lu4242 ]
          Fix Version/s 2.0.5-SNAPSHOT [ 12316168 ]
          Leonardo Uribe made changes -
          Fix Version/s 2.0.5 [ 12316346 ]
          Fix Version/s 2.0.5-SNAPSHOT [ 12316168 ]
          Leonardo Uribe made changes -
          Status Resolved [ 5 ] Closed [ 6 ]


            • Assignee:
              Leonardo Uribe
              Michael Freedman
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: