[ 
https://issues.apache.org/jira/browse/TRINIDAD-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834287#action_12834287
 ] 

Max Starets commented on TRINIDAD-1723:
---------------------------------------

The issue is that WLS is not loading faces-bean.properties from the impl jar, 
so we get a wrong FacesBean bean created for CorePanelPage.
Prior to Blake's change (revision 901411), we had only one 
faces-bean.properties in the impl jar. That worked fine in both Jetty and WLS. 
Since 901411, we have two faces-bean.properties files - one in the impl jar, 
and one in the api. 

FacesBeanFactory._initializeBeanTypes() calls  _getClassLoader().getResources( 
"META-INF/faces-bean.properties"); Jetty will return two URLs (one for 
faces-bean.properties in the api and one in impl), while WLS - only one (in the 
api).  The behavior of WLS seems wrong to me.

It looks like the faces-bean.properties is required for some unit tests in the 
API package. A temporary workaround for WLS would be to copy all entries from 
the impl's faces-bean.properties into the api's faces-bean.properties and 
building with tests disabled.

> Trinidad 2: ClassCastEXception while running componentDemos.jspx
> ----------------------------------------------------------------
>
>                 Key: TRINIDAD-1723
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1723
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 2.0.0-alpha-2
>            Reporter: Max Starets
>
> Grab the latest trinidad-2.0.x branch and try running componentDemos.jspx. 
> The following exception will be thrown:
> java.lang.ClassCastException: 
> org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode cannot be cast 
> to org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode
>       at 
> org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode.__getAdapter(UIXComponentUINode.java:439)
>       at 
> org.apache.myfaces.trinidadinternal.uinode.UINodeRendererBase.encodeEnd(UINodeRendererBase.java:65)
>       at 
> org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:852)
>       at 
> org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:70)
>       at 
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:509)
>       at 
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeAllChildren(CoreRenderer.java:531)
>       at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:70)
>       at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:151)
>       at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:153)
>       at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:80)
>       at 
> org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:546)
>       at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer.encodeAll(DocumentRenderer.java:82)
> This does not seem to be JSF 2 specific, but I have not had time to try it on 
> the latest MAIN.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to