myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Weßendorf (JIRA) <...@myfaces.apache.org>
Subject [jira] Updated: (TRINIDAD-134) StateManagerImpl is not fully compatible with JSR-301
Date Fri, 26 Oct 2007 05:34:50 GMT

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

Matthias Weßendorf updated TRINIDAD-134:
----------------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> 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: Matthias Weßendorf
>             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.


Mime
View raw message