[ http://issues.apache.org/jira/browse/MYFACES-1383?page=comments#action_12428849 ] Scott O'Bryan commented on MYFACES-1383: ----------------------------------------
Ok, this is not en entirely correct. The issue is that the "current" FacesContext which is stored on the session is assumed to be a ServletFacesContextImpl, but it is not. I am looking to see WHY the ServletFacesContextImpl is needed and see if I can't code around it. > 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
