February 2014 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5134) Docs for <s:validateFormattedText> missing

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugi... ] Marek Novotny reassigned JBSEAM-5134: ------------------------------------- Assignee: Marek Novotny > Docs for <s:validateFormattedText> missing > ------------------------------------------ > > Key: JBSEAM-5134 > URL: https://issues.jboss.org/browse/JBSEAM-5134 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Affects Versions: 2.3.0.Final, 2.3.1.Final > Reporter: Sean Flanigan > Assignee: Marek Novotny > > Seam 2.2's reference manual has a brief section in the Seam JSF Controls chapter named <s:validateFormattedText> (under Seam Text): > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/controls.html... > But this section does not exist in Seam 2.3: > http://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html/controls.html... > As far as I can tell, the feature still exists in 2.3; it's just the documentation for it that is missing. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5134) Docs for <s:validateFormattedText> missing

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-5134: --------------------------------------- documentation is still commented so we need to uncomment it. > Docs for <s:validateFormattedText> missing > ------------------------------------------ > > Key: JBSEAM-5134 > URL: https://issues.jboss.org/browse/JBSEAM-5134 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Affects Versions: 2.3.0.Final, 2.3.1.Final > Reporter: Sean Flanigan > > Seam 2.2's reference manual has a brief section in the Seam JSF Controls chapter named <s:validateFormattedText> (under Seam Text): > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/controls.html... > But this section does not exist in Seam 2.3: > http://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html/controls.html... > As far as I can tell, the feature still exists in 2.3; it's just the documentation for it that is missing. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5134) Docs for <s:validateFormattedText> missing

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-5134: --------------------------------------- [~sflanigan] it exists and both usages should work fine. When we started to use seam-cdk-helper plugin it was again generated correctly into s.taglib.xml so Seam 2.3.0.CR1 and later have it again. I will uncomment the documentation part too > Docs for <s:validateFormattedText> missing > ------------------------------------------ > > Key: JBSEAM-5134 > URL: https://issues.jboss.org/browse/JBSEAM-5134 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Affects Versions: 2.3.0.Final, 2.3.1.Final > Reporter: Sean Flanigan > > Seam 2.2's reference manual has a brief section in the Seam JSF Controls chapter named <s:validateFormattedText> (under Seam Text): > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/controls.html... > But this section does not exist in Seam 2.3: > http://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html/controls.html... > As far as I can tell, the feature still exists in 2.3; it's just the documentation for it that is missing. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5134) Docs for <s:validateFormattedText> missing

by Sean Flanigan (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugi... ] Sean Flanigan commented on JBSEAM-5134: --------------------------------------- So, to confirm, are you saying that {{<s:validateFormattedText>}} does not in fact exist in Seam 2.3? But {{<f:validator validatorId="org.jboss.seam.ui.FormattedTextValidator"/>}} should work? > Docs for <s:validateFormattedText> missing > ------------------------------------------ > > Key: JBSEAM-5134 > URL: https://issues.jboss.org/browse/JBSEAM-5134 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Affects Versions: 2.3.0.Final, 2.3.1.Final > Reporter: Sean Flanigan > > Seam 2.2's reference manual has a brief section in the Seam JSF Controls chapter named <s:validateFormattedText> (under Seam Text): > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/controls.html... > But this section does not exist in Seam 2.3: > http://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html/controls.html... > As far as I can tell, the feature still exists in 2.3; it's just the documentation for it that is missing. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5134) Docs for <s:validateFormattedText> missing

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-5134: --------------------------------------- That Seam tag is commented due https://issues.jboss.org/browse/JBSEAM-4955 Look at: https://github.com/seam2/jboss-seam/blob/feb6021bb29f33c4d63955f556b623f1... > Docs for <s:validateFormattedText> missing > ------------------------------------------ > > Key: JBSEAM-5134 > URL: https://issues.jboss.org/browse/JBSEAM-5134 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Affects Versions: 2.3.0.Final, 2.3.1.Final > Reporter: Sean Flanigan > > Seam 2.2's reference manual has a brief section in the Seam JSF Controls chapter named <s:validateFormattedText> (under Seam Text): > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/controls.html... > But this section does not exist in Seam 2.3: > http://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html/controls.html... > As far as I can tell, the feature still exists in 2.3; it's just the documentation for it that is missing. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5134) Docs for <s:validateFormattedText> missing

by Sean Flanigan (JIRA)

Sean Flanigan created JBSEAM-5134: ------------------------------------- Summary: Docs for <s:validateFormattedText> missing Key: JBSEAM-5134 URL: https://issues.jboss.org/browse/JBSEAM-5134 Project: Seam 2 Issue Type: Bug Components: Documentation Issues Affects Versions: 2.3.1.Final, 2.3.0.Final Reporter: Sean Flanigan Seam 2.2's reference manual has a brief section in the Seam JSF Controls chapter named <s:validateFormattedText> (under Seam Text): http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/controls.html... But this section does not exist in Seam 2.3: http://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html/controls.html... As far as I can tell, the feature still exists in 2.3; it's just the documentation for it that is missing. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-339) Catch attempts to use BeanManager during application initialization under Weld 2.0

by Lucas Ventura Carro (JIRA)

[ https://issues.jboss.org/browse/SOLDER-339?page=com.atlassian.jira.plugin... ] Lucas Ventura Carro commented on SOLDER-339: -------------------------------------------- [~yangju] SOLDER-322 solves your problem. Anyway, non-portable mode is the only workaround? There is no patch to use correctly CDI 1.1 spec? > Catch attempts to use BeanManager during application initialization under Weld 2.0 > ---------------------------------------------------------------------------------- > > Key: SOLDER-339 > URL: https://issues.jboss.org/browse/SOLDER-339 > Project: Solder > Issue Type: Bug > Affects Versions: 3.1.0.Final > Environment: JBoss 7.1.1 w/ Weld 2.0.0.Beta2 > Reporter: Ken H > > The exception prevents application from starting. > org.jboss.weld.exceptions.IllegalStateException: WELD-001332 BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerInitialized(BeanManagerProxy.java:148) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:78) > at org.jboss.solder.exception.control.HandlerMethodImpl.getBean(HandlerMethodImpl.java:154) > at org.jboss.solder.exception.control.HandlerMethodImpl.<init>(HandlerMethodImpl.java:138) > at org.jboss.solder.exception.control.extension.CatchExtension.findHandlers(CatchExtension.java:102) > at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:268) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:264) > at org.jboss.weld.annotated.runtime.InvokableAnnotatedMethod.invokeOnInstance(InvokableAnnotatedMethod.java:82) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:97) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:276) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:134) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:263) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:238) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:242) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:173) > at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:47) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:134) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:109) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:69) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38) > at org.jboss.weld.bootstrap.events.ProcessManagedBeanImpl.fire(ProcessManagedBeanImpl.java:30) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessBean(ContainerLifecycleEvents.java:154) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:145) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:133) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:309) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:265) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:446) > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:92) > at org.jboss.as.weld.services.WeldService.start(WeldService.java:77) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF generates exception javax.faces.FacesException: com.sun.faces.lifecycle.ClientWindowFactoryImpl

by deepak vohra (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugi... ] deepak vohra commented on JBSEAM-5133: -------------------------------------- For the Multi-JSF "The final artifact in the target directory will be called install-mojarra-1.2_15.zip. Rename it to install-mojarra-1.2_15.cli." install-mojarra-1.2_15.zip may be renamed to install-mojarra-1.2_15.cli.zip, but how would install-mojarra-1.2_15.zip be renamed to install-mojarra-1.2_15.cli? > 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF generates exception javax.faces.FacesException: com.sun.faces.lifecycle.ClientWindowFactoryImpl

by deepak vohra (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugi... ] deepak vohra commented on JBSEAM-5133: -------------------------------------- Thanks. JSF 2 is supported with Seam 2.3 but Seam is not developed for Java EE 7. Seam 3 has been suspended, which makes Seam not a WildFly supported framework. > 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF generates exception javax.faces.FacesException: com.sun.faces.lifecycle.ClientWindowFactoryImpl

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugi... ] 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2014