[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-164.
--------------------------------------------
Fix Version/s: 1.0.1
2.0.0
Resolution: Fixed
Scope management has been changed/fixed so a scope is only removed when its
actually needs to be.
> Bridge shouldn't notify (bridge) request scope attrbiutes that they are being
> destroyed if only updating the scope at the end of a request
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-164
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-164
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0, 2.0.0-beta
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 1.0.1, 2.0.0
>
>
> The request scope is maintained in a Map of (key, Map) pairs where key is the
> scopeId and Map is the scopeMap -- a Map containing all the current request
> attributes managed in the bridge request scope. The bridge shouldn't notify
> attributes in this scopeMap merely because the Map is being replaced/updated
> -- as the bridge does this at the end of every request. (I.e. the bridge
> lifecyle restores the real request scope from this Map at the beginning of
> the request and then creates a new Map of the request scope at the end of the
> request which it pushes back. As this new Map really is just an updated
> version of the original -- release notification isn't desired/shouldn't be
> done. But it is. So fix it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
