[ 
https://issues.apache.org/jira/browse/MYFACES-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807066#comment-13807066
 ] 

Dipali Pandya commented on MYFACES-3066:
----------------------------------------

Thank you. Perhaps this is not exactly the issue I am experiencing then, since 
the problem was not solved. I am trying to use the rich faces calendar widget 
in a portlet. I am using the MyFaces 2.0 container which comes with websphere 
application server 8. The calendar widget renders correctly however, the 
<extension> element id comes back prefixed with a portlet namespace. This is 
causing the richfaces js to not parse the response correctly. It seems related 
to the following richfaces bug https://issues.jboss.org/browse/RF-11365, which 
mentions something about modifying the encodeNameSpace method. I thought this 
might be it. Does this sound familiar? Is there a different bug to track this 
issue?

> CLONE - UIView.createUniqueId shouldn't call encodeNameSpace to build the id 
> (1.2.x branch).
> --------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3066
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3066
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 1.2.10, 2.0.4
>            Reporter: Michael Freedman
>            Assignee: Leonardo Uribe
>             Fix For: 1.2.11
>
>
> 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 ....



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to