You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Michael Freedman (JIRA)" <de...@myfaces.apache.org> on 2010/02/11 18:14:28 UTC

[jira] Resolved: (PORTLETBRIDGE-115) Reacquire preexistingRequestAttributes in renderRedirect after FacesContext.release

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

Michael Freedman resolved PORTLETBRIDGE-115.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

> Reacquire preexistingRequestAttributes in renderRedirect after FacesContext.release
> -----------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-115
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-115
>             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
>
>
> As FacesContext.release now releases all request attributes that didn't exist prior to the bridge being called we need to reconstruct the PreExistingRequestAttributes list after calling facesContext.release() in the renderRedirect (BridgeImpl) as this attribute is among those relese() removes.

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