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/03/18 23:02:27 UTC

[jira] Created: (PORTLETBRIDGE-132) Websphere claims there are no private parameters in an action but we expect them

Websphere claims there are no private parameters in an action but we expect them
--------------------------------------------------------------------------------

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


The bridge restricts the view of parameters via the ExternalContext to the privateParameters.  On websphere this is coming back null during an action causing the bridge to break.  To work around this change the map code to get the full parameter set and remove the public parameters and return the difference.

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


[jira] Resolved: (PORTLETBRIDGE-132) Websphere claims there are no private parameters in an action but we expect them

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

Michael Freedman resolved PORTLETBRIDGE-132.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Websphere 6.1 incorrectly returns a null/empty map for getPrivateParameterMap during an action.  To work around this the bridge's param map utility classes now check to see if if a null/emtpty map is returned and if so, computes the true return value by getting the fully set of parameters and then exlcuding those that are public render parameters. 

> Websphere claims there are no private parameters in an action but we expect them
> --------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-132
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-132
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 2.0.0
>
>
> The bridge restricts the view of parameters via the ExternalContext to the privateParameters.  On websphere this is coming back null during an action causing the bridge to break.  To work around this change the map code to get the full parameter set and remove the public parameters and return the difference.

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


[jira] Resolved: (PORTLETBRIDGE-132) Websphere claims there are no private parameters in an action but we expect them

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

Michael Freedman resolved PORTLETBRIDGE-132.
--------------------------------------------

    Resolution: Fixed

Adjusted code as mentioned -- not as efficient but should always work.

> Websphere claims there are no private parameters in an action but we expect them
> --------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-132
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-132
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 2.0.0
>
>
> The bridge restricts the view of parameters via the ExternalContext to the privateParameters.  On websphere this is coming back null during an action causing the bridge to break.  To work around this change the map code to get the full parameter set and remove the public parameters and return the difference.

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


[jira] Reopened: (PORTLETBRIDGE-132) Websphere claims there are no private parameters in an action but we expect them

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

Michael Freedman reopened PORTLETBRIDGE-132:
--------------------------------------------


> Websphere claims there are no private parameters in an action but we expect them
> --------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-132
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-132
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 2.0.0
>
>
> The bridge restricts the view of parameters via the ExternalContext to the privateParameters.  On websphere this is coming back null during an action causing the bridge to break.  To work around this change the map code to get the full parameter set and remove the public parameters and return the difference.

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