[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-158.
--------------------------------------------
Fix Version/s: 2.0.0-beta
Resolution: Fixed
Trick to to set a flag when a redirect is detected to indicate we need to
remove the scope. At end of event processing if this flag is set then remove
the scope from the internal data structure.
> Portlet 2.0 Bridge event redirect doesn't work because scope isn't cleared
> --------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-158
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-158
> 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-beta
>
>
> Problem is the bridge automatically copies render parameters to the response
> at the beginning of the request. If a redirect occurs the bridge request
> scope should cleared/dropped -- however because its carried in a render
> parameter its already carried forward so it stays around.
> Fix: on a redirect clear the request scope. Since there is no way to remove
> a render parameter once added, the easiest thing to do is to actually remove
> the scope from the internal data structure. This way when we try to restore
> the scope on the render it won't be there and we will just start a new one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
