This now works with 4.2 and Portal 2.6.1GA, using the steps defined in JBoss's
documentation for not inheriting Faces into an application.
Thanks to the JBoss Portal team for there hard work,
ERIC GANDT
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070113#40
The problem seems to be that you are loading JSF from two different spots
resulting in java.lang.IllegalArgumentException: Class
org.jboss.portal.faces.portlet
.JSFMetaBridgeViewHandlerImpl is no javax.faces.application.ViewHandler (in
essence a ClassCastException) due to the fact that the class
I looked at the suggested reading and tried a number of suggested options,
The best options seems to be adding
|
| org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL
| true
|
|
I assume that since my application includes a portlet.xml file (and also
includes portlets), this is the caus
First you shouldn't rely on a specific implementation but delegate your work to
the underlying implementation
Since you are stuck with MyFaces , i suggest you have a look at:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces
View the original post :
http://www.jboss.com/index.html?module=bb
My problem is that our product is desgined to work cross platform, and
currently supports both SUN Portal, WebSphere Portal and WebLogic Portal as
well as Jboss Portal. Since we are cross platform we create our own extension
of myfaces which we then load with a contextroot of /faces, we also use
"egandt" wrote : First off there is a Wiki document at
http://wiki.jboss.org/wiki/Wiki.jsp?page=Running2.6WithJBossAS4.2.xAndMyFaces
|
This is only needed if you intend to use MyFaces instead of JSF RI globally, at
the application-server level.
"egandt" wrote : Which appears to cover this to
