[ 
https://issues.apache.org/jira/browse/PORTLETBRIDGE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Freedman resolved PORTLETBRIDGE-55.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

PortletNamingContainer has been updated to indicate it implements 
NamingContainer.  Also minor javadoc fixes to the Preferences.java.

> PortletNamingContainer broken
> -----------------------------
>
>                 Key: PORTLETBRIDGE-55
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-55
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0-alpha, 1.0.0-alpha-2, 1.0.0-alpha-3, 1.0.0, 2.0.0
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> I while back we decided that we would no longer identify that a UIViewRoot 
> was a PortletNamingContainer by whether it implemented an interface or not -- 
> rather we switched to using an annotation.  When we did this (removed the 
> interface I inadvertently removed the entity that indicated it implemented 
> NamingContainer.  I.e. the API provided class didn't "implement 
> NamingContainer".  Hence Faces never saw this UIViewRoot as a namingContianer 
> and hence component ids weren't being qualified by the portlet namespace.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to