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 17:56:29 UTC

[jira] Created: (PORTLETBRIDGE-119) Portlet 2.0 Bridge redisplay after redirect needs to update redirects PublicRenderParameter Map if redisplay sends new/different PRPs

Portlet 2.0 Bridge redisplay after redirect needs to update redirects PublicRenderParameter Map if redisplay sends new/different PRPs
-------------------------------------------------------------------------------------------------------------------------------------

                 Key: PORTLETBRIDGE-119
                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-119
             Project: MyFaces Portlet Bridge
          Issue Type: Bug
          Components: Impl
    Affects Versions: 2.0.0-alpha
            Reporter: Michael Freedman
            Assignee: Michael Freedman


Normally in a redisplay following a render redirect the bridge will receive the same public render parameters it received in the request that triggered the redirect.  However if the value of one or more PRPs has changed since redirect (and before the redisplay) the bridge needs to detect the changes and apply them to the one's being managed for the redirect (cache).  I.e. the bridge needs to cache the existing PRPs when the render redirect occurs.  If we get a redisplay it compares the incoming PRPs to the cached PRPs.  If there are differences it applies them to the cached redirect URL.

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

[jira] Resolved: (PORTLETBRIDGE-119) Portlet 2.0 Bridge redisplay after redirect needs to update redirects PublicRenderParameter Map if redisplay sends new/different PRPs

Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Freedman resolved PORTLETBRIDGE-119.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Does what the bug indicated.

> Portlet 2.0 Bridge redisplay after redirect needs to update redirects PublicRenderParameter Map if redisplay sends new/different PRPs
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-119
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-119
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 2.0.0
>
>
> Normally in a redisplay following a render redirect the bridge will receive the same public render parameters it received in the request that triggered the redirect.  However if the value of one or more PRPs has changed since redirect (and before the redisplay) the bridge needs to detect the changes and apply them to the one's being managed for the redirect (cache).  I.e. the bridge needs to cache the existing PRPs when the render redirect occurs.  If we get a redisplay it compares the incoming PRPs to the cached PRPs.  If there are differences it applies them to the cached redirect URL.

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