[
https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943658#comment-12943658
]
Marek Novotny commented on JBSEAM-5133:
---------------------------------------
Well, JSF 2 and I would be more precise that Seam 2.3 supports JSF 2.0 and 2.1,
but due some new feature not JSF 2.2. And Seam 2.3 is only in maintenance phase
so no new features will be developed.
Why do you need to use Wildfly instead of EAP6 or JBoss AS 7? As you wrote it
doesn't bundle by default JSF 1 nor older JSF 2.1/2.0 libraries.
Wildfly is Java EE 7 server on bleeding edge and it is obviously able to run
old applications but not on new Java EE 7 implementations. Have you seen
https://community.jboss.org/wiki/DesignOfWildFlyMulti-JSFFeature which
describes in details installing different version from default bundle?
> Seam 2.2 with JSF generates exception javax.faces.FacesException:
> com.sun.faces.lifecycle.ClientWindowFactoryImpl
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-5133
> URL: https://issues.jboss.org/browse/JBSEAM-5133
> Project: Seam 2
> Issue Type: Feature Request
> Environment: JBoss as 8
> Seam 2.2
> Eclipse 4.3
> Maven 3.4
> Reporter: deepak vohra
>
> Seam 2.2 & JSF application on JBoss AS 8 generates exception
> SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service
> thread 1-1) Critical error
> during deployment: : com.sun.faces.config.ConfigurationException: Factory
> 'javax.faces.lifecycle.ClientWindowFactory' was not configured properly.
> at
> com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist
> (FactoryConfigProcessor.java:330) [jsf-impl-2.2.4-jbossorg-1.jar:]
> at
> com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:236)
> [jsf-
> impl-2.2.4-jbossorg-1.jar:]
> at
> com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435)
> [jsf-impl-2.2.4-jbossorg-1.jar:]
> at
> com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:214)
> [jsf-impl-2.2.4-
> jbossorg-1.jar:]
> at
> io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
>
> [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
> at
> io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:182)
> [undertow-
> servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
> at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext
> (UndertowDeploymentService.java:86)
> at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start
> (UndertowDeploymentService.java:71)
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [rt.jar:1.7.0_21]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: javax.faces.FacesException:
> com.sun.faces.lifecycle.ClientWindowFactoryImpl
> at
> javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:723)
> [jboss-jsf-api_2.2_spec-
> 2.2.4.jar:2.2.4]
> at
> javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:553)
> [jboss-jsf-api_2.2_spec-
> 2.2.4.jar:2.2.4]
> at javax.faces.FactoryFinder.access$500(FactoryFinder.java:140)
> [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at
> javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:1120)
> [jboss-jsf-api_2.2_spec-
> 2.2.4.jar:2.2.4]
> at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:379)
> [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at
> com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist
> (FactoryConfigProcessor.java:328) [jsf-impl-2.2.4-jbossorg-1.jar:]
> ... 12 more
> Caused by: java.lang.UnsupportedOperationException
> at
> javax.faces.application.Application.subscribeToEvent(Application.java:1797)
> [jboss-jsf-api_2.2_spec-
> 2.2.4.jar:2.2.4]
> at
> org.jboss.as.jsf.injection.weld.ForwardingApplication.subscribeToEvent(ForwardingApplication.java:373)
>
> [wildfly-jsf-injection-8.0.0.CR1.jar:8.0.0.CR1]
> at
> com.sun.faces.lifecycle.ClientWindowFactoryImpl.<init>(ClientWindowFactoryImpl.java:62)
> [jsf-impl-
> 2.2.4-jbossorg-1.jar:]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) [rt.jar:1.7.0_21]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>
> [rt.jar:1.7.0_21]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>
> [rt.jar:1.7.0_21]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> [rt.jar:1.7.0_21]
> at java.lang.Class.newInstance0(Class.java:374) [rt.jar:1.7.0_21]
> at java.lang.Class.newInstance(Class.java:327) [rt.jar:1.7.0_21]
> at
> javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:721)
> [jboss-jsf-api_2.2_spec-
> 2.2.4.jar:2.2.4]
> ... 17 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
