[jira] Resolved: (PORTLETBRIDGE-63) Rework mechanism for creating a UIViewRoot of type PortletNamingContainerUIViewRoot

["Michael Freedman (JIRA)" <de...@myfaces.apache.org>]

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

Michael Freedman resolved PORTLETBRIDGE-63.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

Code now relies primarily on a bridge impl of the Application object to override the createComponent.  Note:  there is still a backdoor in the VH.createView to do this work manually to meet the spec.

> Rework mechanism for creating a UIViewRoot of type PortletNamingContainerUIViewRoot
> -----------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-63
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-63
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0-beta, 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> Upon advice from the EG its recommended that we implement the behavior in the bridge that ensures a PortletNamingContainerUIViewRoot is created if the appropriate conditions apply by overriding Application.createComponent.  Because of spec language, the bridge's ViewHandler.createView will also keep code that: first delegates to create the view -- if this created view isn't a PortletNamingContainer and meets the conditions (i.e. somehow our Application.createComponent wasn't called) we retry creating after manually setting the componentType.

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