myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fernando Silva Lozano (JIRA)" <>
Subject [jira] Reopened: (MYFACES-2395) Cant' run two JSF portlets on the same portal page
Date Mon, 31 May 2010 21:31:41 GMT


Fernando Silva Lozano reopened MYFACES-2395:

I don't think this is a problem related to classpath. Maybe you was too quick in dismissing
this bug. Do you have any evidence this isactually a classpath problem? Because my evidence
tells it isn't.

JBoss supports the use of alternative JSF implementations, provided inside the application
WAR package. See that my both test apps include, on web.xml 


If you do that, JBoss bundled Mojarra is not visible inside the web app classloader.

The jboss logs show that the MyFaces classes are being initialized for both apps. And the
error stack traces does not includes any Mojarra classes, only MyFaces, eXo, Tomcat and JBoss
AS ones, as expected.

By the way other portal software don't support MyFaces, telling it won't work inside portlets
without giving details. For example, Oracle iAS uses MyFaces as the bundled JSF implementation,
but Oracle Portal states you have to use the Sun RI instead of MyFaces.

I guess this is the issue behind supporting MyFaces on portlets, because everything I tried
worked as long as there where only one JSF portlet on the same portal page. But nothing works
when there are more than one, if I do use MyFaces.

> Cant' run two JSF portlets on the same portal page
> --------------------------------------------------
>                 Key: MYFACES-2395
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: Portlet_Support
>         Environment: JDK 1.5, JBoss AS 4.2.3, eXo PC 2.0.5 or eXO WCM 1.0 or eXO WCM
>            Reporter: Fernando Silva Lozano
>            Assignee: Leonardo Uribe
>         Attachments: hora-mundo-jsf.war, todo-jsf.war
> Running two portlets in the same portal page, using JSF and the MyFaces Portlet Bridge
(which is the RI for JSR-301, the JSF Portlet Bridge)  yelds the error bellow for the second
> 19:31:39,704 ERROR [portletcontainer] exception returned by processAction() or render()
> javax.portlet.PortletException: doBridgeDispatch failed:  error from Bridge in executing
the request
>      at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(
>      at javax.portlet.faces.GenericFacesPortlet.doRenderDispatchInternal(
>      at javax.portlet.faces.GenericFacesPortlet.doView(
>      at javax.portlet.GenericPortlet.doDispatch(
>      at javax.portlet.faces.GenericFacesPortlet.doDispatch(
>      at javax.portlet.GenericPortlet.render(
>      at
>     at
> ...
>  Caused by: javax.portlet.faces.BridgeException: java.lang.ClassCastException: org.apache.myfaces.renderkit.RenderKitFactoryImpl
>      at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(
>      at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRequest(
>      at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(
>      ... 63 more
> Caused by: java.lang.ClassCastException: org.apache.myfaces.renderkit.RenderKitFactoryImpl
>      at org.apache.myfaces.shared_impl.renderkit.RendererUtils.getResponseStateManager(
>      at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.isPostback(
>      at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(
>      at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(
>      at org.apache.myfaces.lifecycle.LifecycleImpl.execute(
>      at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(
>      ... 65 more
> This exception allways happen with the second portlet on the page, whichever it is. I
tried with many portlets, but so you can reproduce the problem I'm attaching the wars for
two very simple portlets.
> I'm filling this under MyFaces Core instead of Portlet Bridge because the same applications,
if deployed to use Mojarra (included in JBoss AS 4.2) and the same portelt bridge jars, work

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

View raw message