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-118) BridgeRenderRequestWrapper needs to individually manage public and private parameters

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

Michael Freedman resolved PORTLETBRIDGE-118.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Now manages each Map individually.

> BridgeRenderRequestWrapper needs to individually manage public and private parameters
> -------------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-118
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-118
>             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
>
>
> BridgeRenderRequestWrapper is used (in part) to handle render redirect.  The bridge wraps the original request with this one and overrides what appears to be the request parameters with the one's in the redirect url.  As Portlet 2.0 distinguishes between public and private parameters, this wrapper needs to properly manage the parameters so that the APIs for getting the parameters, private params, and public params, all do the right thing.

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