[
https://issues.apache.org/jira/browse/MYFACES-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3039.
-------------------------------------
Resolution: Fixed
> MyFaces broken in Portlet environment: Fails to support extendable
> FacesContextFactory/FacesContext/ExternalContext
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-3039
> URL: https://issues.apache.org/jira/browse/MYFACES-3039
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Reporter: Michael Freedman
> Assignee: Leonardo Uribe
> Fix For: 2.0.5-SNAPSHOT
>
>
> JSF 2.0 improved the definition/handling of the instantiation of the
> FacesContext allowing non-servlet environments to wrap the base/core impl.
> This was done because most of the FacesContext apis are inherently runtime
> environment neutral -- allowing the portlet bridge to not have to
> duplicate/reimplement and maybe get wrong base core function. Unfortunately
> MyFaces doesn't conform to this change and hence the Portlet Bridge can't run
> in the MyFaces environment.
> Basically the bridge expects to be able to delegate from its
> FacesContextFactoryImpl.getFacesContext and then wrap the returned
> FacesContext with its own. This requires the underlying core impl to be
> runtime (servlet/portlet) neutral during the creation process. The bridge
> will wrap the FacesContext and supply its own ExternalContext such that any
> servlet dependent impl in the core FacesContext/ExternalContext will be
> hidden by overrides.
> FYI ... until this is addressed I can't begin any testing of the bridge on
> MyFaces.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
