[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012588#comment-13012588
]
Michael Freedman commented on PORTLETBRIDGE-203:
------------------------------------------------
We will have to discuss/debate this one. Turns out there are some Faces
internal FacesContext attributes that can't be preserved across FacesContext
releases and there are others that must. In addition we need to
discuss/understand to what degree application developers are using this scope
and expect/require that it last until the entire action/render occurs.
Basically -- this scope is a mess for the bridge as its normal behavior is to
release the FacesContext at the end of the action and start a new one in
render. I really want to avoid having to support a similar include/exclude
mechanism as the request scope for any new scope.
> Proposal for 3.0 IMPL: Preserve and restore JSF2 FacesContext attributes in
> BridgeRequestScope
> ----------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-203
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-203
> Project: MyFaces Portlet Bridge
> Issue Type: New Feature
> Components: General
> Affects Versions: 3.0.0
> Reporter: Neil Griffin
> Assignee: Michael Freedman
>
> The JSF 2.0 API introduced a getAttributes() method on FacesContext:
> http://javaserverfaces.java.net/nonav/docs/2.0/javadocs/javax/faces/context/FacesContext.html#getAttributes()
> These values need to be preserved in the BridgeRequestScope. For more
> information on implementation details, search for
> "BRIDGE_REQ_SCOPE_ATTR_FACES_CONTEXT_ATTRIBUTES" in the following Java class:
> http://svn.portletfaces.org/svn/portletfaces/bridge/portletfaces-bridge-impl/trunk/src/main/java/org/portletfaces/bridge/scope/BridgeRequestScopeImpl.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
