Use MyFaces 1.2. That exception suggests to me that you've still got conflicting jsf implementations in JBoss AS.
I have added this entry to the web.xml:
<context-param> <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name> <param-value>true</param-value> </context-param>
myfaces-api.jar and myfaces-impl.jar I have added to WEB-INF/lib in war file.
JBoss AS 4.2.2 is newly installed and the application is newly generated by seam-gen. Without any changes. No other applications on server. Where should I search a solution?
Are you sure that your third party library needs the MyFaces impl? Which one is it? The only one I know of that actually referred to MyFaces core impl classes was old versions of Tomahawk.
If you are still getting conflicts as Pete suggests then you should try removing the JSF impl from /deploy/jboss-web.deployer/jsf-libs. If you do that then you will also need to edit /deploy/jboss-web.deployer/conf/web.xml and comment out these listeners:
<!-- Configures JSF for a web application if the javax.faces.webapp.FacesServlet is declared --> <!-- in web.xml. --> <listener> <listener-class>org.jboss.web.jsf.integration.config.JBossJSFConfigureListener</listener-class> </listener> <!-- Listens to all web app lifecycle events so that @PreDestroy can be called on --> <!-- JSF managed beans that go out of scope. You can comment this out if you --> <!-- don't use JSF or you don't use annotations on your managed beans. --> <listener> <listener-class>com.sun.faces.application.WebappLifecycleListener</listener-class> </listener>
Hope that helps,
It is fck-faces. I have changed dependency to tomahawk and now it's working.
I have the same problem. When I comment listeners in web.xml I have error
Failed to load engineOptionsClass
at sun.reflect.GeneratedConstructorAccessor47.newInstance(Unknown Source)