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 2009/08/18 23:33:14 UTC
[jira] Resolved: (PORTLETBRIDGE-94) No render after action in some
portlet containers
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-94.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Added the getPrivateParameterMap impl to the wrapper.
Note: this only impacts the render wrapper. There is no resource wrapper because parameters aren't carried forward into it.
> No render after action in some portlet containers
> -------------------------------------------------
>
> Key: PORTLETBRIDGE-94
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-94
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 2.0.0-alpha, 2.0.0
> Reporter: Michael Freedman
> Fix For: 2.0.0
>
>
> In the latest Oracle WLP portlet container, the render following an action doesn't render.
> This occurs because the VIEW_STATE parameter isn't seen by the bridge and hence Faces thinks we aren't rendering following a postback. The problem occurs in the requestwrapper(s). Though the VIEW_STATE param is passed to the wrapper (its carried across in the request scope), the wrapper doesn't implement getPrivateParameterMap -- and hence its not added to the Map when this method is called by the bridge's externalContext when it puts together the param map.
> Fix is to implement the method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.