[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016463#comment-13016463
]
Michael Freedman commented on PORTLETBRIDGE-203:
------------------------------------------------
I have found that the 329/301 bridge methodology of caching the UIViewRoot and
releasing the FacesContext at the end of the action and then getting the render
to use the cached UIViewRoot in a new FacesContext will not work consistently
in JSF 3.0. Each release of Mojarra or Myfaces I get changes the issue I ran
into -- yes first it was just the need to carry some of the FacesContext
attributes forward -- but now there are issues with attributes stored on the
UiViewRoot itself that have been released underneath these references in the
prior facesContext.release.
So I think the bridge is going to have to change to explicitly save and restore
the view across the action/render -- at which point we won't need to
preserve/restore the JSF2 FacesContext attrs anymore.
> 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
