[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155497#comment-13155497
]
Michael Freedman commented on PORTLETBRIDGE-221:
------------------------------------------------
Fixed in 2.0 Trunk by changing implementation back to the original. The Bridge
no longer updates the scope in a render request, rather it leaves the existing
scope unchanged except for attributes it maintains/manages such as the
VIEW_STATE_PARAM.
Fixed in Oracle branch by explicitly excluding (in code) trinidad and adf
attributes during a render phase. Code doesn't exclude/remove trinidad/adf
attrs that were carried forward from the action, just those added during the
render.
3.0 work is still pending.
> Add explicit exclusions for trinidad in 329 branch
> ---------------------------------------------------
>
> Key: PORTLETBRIDGE-221
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-221
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 2.0.0
> Reporter: Michael Freedman
> Assignee: Michael Freedman
>
> We are running into problems with a user of the 329 branch codeline when
> using with extra Faces (componentkit) extensions. The problem is the bridge
> is updating the bridge scope at the end of the render request pushing all new
> attributes created during the render into the scope. These extensions are
> expecting this so numerous request scope attrs which are "flags" that
> something is initialized/done are inappropriately being carried forward and
> used causing malfunctions. At the moment we don't want to just blanket
> reverse the code from saving the scope at the end of the render -- instead
> deciding the safest thing is to just exclude the specific packages that might
> exist.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
