[jira] Commented: (TRINIDAD-134) StateManagerImpl is not fully compatible with JSR-301

["Scott O'Bryan (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TRINIDAD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537174 ] 

Scott O'Bryan commented on TRINIDAD-134:
----------------------------------------

This is a 1.2 only patch.  Can we get this into 1.2.3 before it closes?

> StateManagerImpl is not fully compatible with JSR-301
> -----------------------------------------------------
>
>                 Key: TRINIDAD-134
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-134
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Portlet
>    Affects Versions: 1.2.1-core
>         Environment: JSR-168, JSR-301
>            Reporter: Scott O'Bryan
>            Assignee: Scott O'Bryan
>             Fix For: 1.2.3-core
>
>         Attachments: trinidad-134.patch
>
>
> StateManagerImpl has a performance enhancement that is not compatible with JSR-301.  Inside of the popRoot method inside of org.apache.myfaces.trinidadinternal.application.StateManagerImpl, the view root is retrieved using Application.createComponent();.  The JSR-301 bridge has a special UIViewRoot that, due to limitations in the JSF specification, can only reasonably be retrieved through ViewHandler.createViewRoot().  We either need to try to try to retrieve the UIViewRoot using this mechanism OR we need to disable this performance optimization in a portal environment.

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