[jira] Resolved: (PORTLETBRIDGE-66) Don't restore bridge request scope in render if a client directed view

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

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

Michael Freedman resolved PORTLETBRIDGE-66.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

Code now doesn't restore the scope if the client specifies the particular view target.

> Don't restore bridge request scope in render if a client directed view
> ----------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-66
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-66
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>    Affects Versions: 1.0.0-beta, 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> The bridge allows the portlet to specify the specific view target by setting a request attribute.  This attribute overrides all other encoded/cached targets.   Each time a client directed view is used it shouldn't use an existing bridge request scope as the later is designed to carry over from actions and the former is not.  Code must be updated so the bridge detects it will be using a client directed view in the render and to not restore the scope.

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