myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Freedman (JIRA)" <...@myfaces.apache.org>
Subject [jira] Reopened: (MYFACES-3039) MyFaces broken in Portlet environment: Fails to support extendable FacesContextFactory/FacesContext/ExternalContext
Date Mon, 14 Feb 2011 21:41:57 GMT

     [ https://issues.apache.org/jira/browse/MYFACES-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Freedman reopened MYFACES-3039:
---------------------------------------


Can you clarify what the defaultExternalContext is being used for?  On portlet requests this
seemingly won't be set/used as its the Bridge's ExternalContext that is in use not the core
MyFaces one (which does the attribute put that causes this default stuff to be enabled). 
Basically, I am trying to ensure there isn't a problem in the portlet env in not participating
in this mechanism.

> 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

        

Mime
View raw message