[ http://issues.apache.org/jira/browse/MYFACES-1383?page=comments#action_12445288 ] Scott O'Bryan commented on MYFACES-1383: ----------------------------------------
Looking at this issue again, it seems to me that it would be better to recreate the FacesContext between the execute and render phases of the lifecycle. We would need to preserve messages and some other things, but nothing to difficult to preserve. This would allow "wrappers" to update their wrapping when the external context changes. The one downfall is that this is a pretty major change from the current functionality of the Faces Bridge Portlet although it is more inline with other Bridge Portlets. Anyone have an issue with this? > FacesContextFactoryImpl issue using trinidad any myfaces core > ------------------------------------------------------------- > > Key: MYFACES-1383 > URL: http://issues.apache.org/jira/browse/MYFACES-1383 > Project: MyFaces Core > Issue Type: Bug > Components: Portlet_Support > Affects Versions: 1.1.5-SNAPSHOT > Environment: pluto 1.1-dev, tomcat 5.5.17 running on linux 2.6.17 > Reporter: nicolas kalkhof > > trinidad won´t run in a portlet environment. problem is, that > FacesContextFactoryImpl does not extend > ServletFacesContextImpl. therefore this is an internal myfaces core problem > that could hopefully be fixed. > stacktrace of the crashing portlet using myfaces and trinidad: > javax.portlet.PortletException: > org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.handleExceptionFromLifecycle(MyFacesGenericPortlet.java:253) > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:407) > .... > Nested Exception is java.lang.ClassCastException: > org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:387) > at > net.portlets.logon.LogonPortlet.doView(LogonPortlet.java:88) > .... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
