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/10/16 23:42:31 UTC
[jira] Created: (PORTLETBRIDGE-96) Bridge render handler not
restoring from cached session scope when available
Bridge render handler not restoring from cached session scope when available
----------------------------------------------------------------------------
Key: PORTLETBRIDGE-96
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-96
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: Impl
Affects Versions: 2.0.0-alpha
Reporter: Michael Freedman
Assignee: Michael Freedman
The bridge render handler correctly tries to restore the request scope (id) from the render parameter but then fails to fallback and check/use the one cached in the session if its not there. I.e. If a resource request occurs before a scope is established (first action) the scope is maintained in a session attribute as resources can't write new render parameters. The render code isn't picking up/using this scope.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PORTLETBRIDGE-96) Bridge render handler not
restoring from cached session scope when available
Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-96.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Updated BridgeImpl's render handler to rely on the same getRequestScopeId() method as the resource code -- i.e. one that does the right thing of falling over to check the session if the render parameter isn't there.
> Bridge render handler not restoring from cached session scope when available
> ----------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-96
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-96
> 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
>
>
> The bridge render handler correctly tries to restore the request scope (id) from the render parameter but then fails to fallback and check/use the one cached in the session if its not there. I.e. If a resource request occurs before a scope is established (first action) the scope is maintained in a session attribute as resources can't write new render parameters. The render code isn't picking up/using this scope.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.