From issues at jboss.org  Tue Feb 11 14:29:29 2014
From: issues at jboss.org (deepak vohra (JIRA))
Date: Tue, 11 Feb 2014 14:29:29 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF
 generates exception javax.faces.FacesException:
 com.sun.faces.lifecycle.ClientWindowFactoryImpl
In-Reply-To: <JIRA.12531801.1392146862621@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12531801.1392146862621@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531801.1392146862621.47986.1392146969021@jira02.app.mwc.hst.phx2.redhat.com>

deepak vohra created JBSEAM-5133:
------------------------------------

             Summary: 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

From issues at jboss.org  Tue Feb 11 15:39:28 2014
From: issues at jboss.org (deepak vohra (JIRA))
Date: Tue, 11 Feb 2014 15:39:28 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF
 generates exception javax.faces.FacesException:
 com.sun.faces.lifecycle.ClientWindowFactoryImpl
In-Reply-To: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531801.1392146862000.48121.1392151168769@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943630#comment-12943630 ] 

deepak vohra commented on JBSEAM-5133:
--------------------------------------

Seam 2.3.1 with JSF 2 support also generates the same exception.
                
> 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

From issues at jboss.org  Tue Feb 11 16:05:28 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 11 Feb 2014 16:05:28 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF
 generates exception javax.faces.FacesException:
 com.sun.faces.lifecycle.ClientWindowFactoryImpl
In-Reply-To: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531801.1392146862000.48252.1392152728515@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943640#comment-12943640 ] 

Marek Novotny commented on JBSEAM-5133:
---------------------------------------

I would like to clarify the versions and server you wrote in environment.

JBoss AS 8??? you mean Wildfly 8?

Maven 3.4?? where is that released? Never mind it has no effect on runtime deployment exception.

As you can see java.lang.UnsupportedOperationException  - Seam 2.x doesn't support JSF 2.2, you need to use EAP 6 or JBoss AS 7.1
We haven't tested Seam 2.3.1 on Wildfly because project and framework is not targeting Wildfly primary Java EE 7 container. You should be using CDI instead of Seam 2 DI.

                
> 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

From issues at jboss.org  Tue Feb 11 16:43:28 2014
From: issues at jboss.org (deepak vohra (JIRA))
Date: Tue, 11 Feb 2014 16:43:28 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF
 generates exception javax.faces.FacesException:
 com.sun.faces.lifecycle.ClientWindowFactoryImpl
In-Reply-To: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531801.1392146862000.48319.1392155008580@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943649#comment-12943649 ] 

deepak vohra commented on JBSEAM-5133:
--------------------------------------

JBoss AS 8??? you mean Wildfly 8?
Yes.

But the following post indicates JSF 2 is supported with Seam 2.3
https://community.jboss.org/thread/232960

Which version of Seam does WildFly support and may it be used with JSF 2 or JSF 1.2?
JSF 1.2 not being deployed by default, would the multi-JSF feature would have to be used?
                
> 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

From issues at jboss.org  Tue Feb 11 17:15:31 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 11 Feb 2014 17:15:31 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF
 generates exception javax.faces.FacesException:
 com.sun.faces.lifecycle.ClientWindowFactoryImpl
In-Reply-To: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531801.1392146862000.48365.1392156931000@jira02.app.mwc.hst.phx2.redhat.com>


    [ 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

From issues at jboss.org  Tue Feb 11 17:15:31 2014
From: issues at jboss.org (deepak vohra (JIRA))
Date: Tue, 11 Feb 2014 17:15:31 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF
 generates exception javax.faces.FacesException:
 com.sun.faces.lifecycle.ClientWindowFactoryImpl
In-Reply-To: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531801.1392146862000.48372.1392156931356@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943659#comment-12943659 ] 

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

From issues at jboss.org  Tue Feb 11 18:25:28 2014
From: issues at jboss.org (deepak vohra (JIRA))
Date: Tue, 11 Feb 2014 18:25:28 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5133) Seam 2.2 with JSF
 generates exception javax.faces.FacesException:
 com.sun.faces.lifecycle.ClientWindowFactoryImpl
In-Reply-To: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12531801.1392146862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531801.1392146862000.48456.1392161128878@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943669#comment-12943669 ] 

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

From issues at jboss.org  Thu Feb 13 05:17:29 2014
From: issues at jboss.org (Lucas Ventura Carro (JIRA))
Date: Thu, 13 Feb 2014 05:17:29 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (SOLDER-339) Catch attempts to use
 BeanManager during application initialization under Weld 2.0
In-Reply-To: <JIRA.12482611.1358253164000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12482611.1358253164000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12482611.1358253164000.52819.1392286649961@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SOLDER-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944173#comment-12944173 ] 

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

From issues at jboss.org  Fri Feb 14 00:45:29 2014
From: issues at jboss.org (Sean Flanigan (JIRA))
Date: Fri, 14 Feb 2014 00:45:29 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5134) Docs for
 <s:validateFormattedText> missing
In-Reply-To: <JIRA.12532163.1392356685410@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532163.1392356685410@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532163.1392356685410.55998.1392356729197@jira02.app.mwc.hst.phx2.redhat.com>

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#d0e29219

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#d0e29088

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

From issues at jboss.org  Fri Feb 14 05:23:28 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Fri, 14 Feb 2014 05:23:28 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5134) Docs for
 <s:validateFormattedText> missing
In-Reply-To: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532163.1392356685000.56618.1392373408735@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944566#comment-12944566 ] 

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/feb6021bb29f33c4d63955f556b623f1470ccaf3/seam-reference-guide/src/docbook/en-US/Controls.xml#L841
                
> 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#d0e29219
> 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#d0e29088
> 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

From issues at jboss.org  Sun Feb 16 19:31:47 2014
From: issues at jboss.org (Sean Flanigan (JIRA))
Date: Sun, 16 Feb 2014 19:31:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5134) Docs for
 <s:validateFormattedText> missing
In-Reply-To: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532163.1392356685000.342.1392597107557@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12945054#comment-12945054 ] 

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#d0e29219
> 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#d0e29088
> 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

From issues at jboss.org  Mon Feb 17 04:03:47 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 17 Feb 2014 04:03:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5134) Docs for
 <s:validateFormattedText> missing
In-Reply-To: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532163.1392356685000.608.1392627827995@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12945108#comment-12945108 ] 

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#d0e29219
> 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#d0e29088
> 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

From issues at jboss.org  Mon Feb 17 04:03:48 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 17 Feb 2014 04:03:48 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5134) Docs for
 <s:validateFormattedText> missing
In-Reply-To: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532163.1392356685000.609.1392627828031@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12945109#comment-12945109 ] 

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#d0e29219
> 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#d0e29088
> 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

From issues at jboss.org  Mon Feb 17 04:05:47 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 17 Feb 2014 04:05:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5134) Docs for
 <s:validateFormattedText> missing
In-Reply-To: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532163.1392356685000.614.1392627947596@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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#d0e29219
> 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#d0e29088
> 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

From issues at jboss.org  Mon Feb 17 06:47:48 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 17 Feb 2014 06:47:48 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5134) Docs for
 <s:validateFormattedText> missing
In-Reply-To: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532163.1392356685000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532163.1392356685000.976.1392637668224@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny resolved JBSEAM-5134.
-----------------------------------

    Fix Version/s: 2.3.2.CR1
       Resolution: Done

    
> 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
>             Fix For: 2.3.2.CR1
>
>
> 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#d0e29219
> 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#d0e29088
> 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

From issues at jboss.org  Tue Feb 18 05:21:48 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 18 Feb 2014 05:21:48 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5132) Two XXE security issues in
	Seam remoting
In-Reply-To: <JIRA.12530011.1390319224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530011.1390319224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530011.1390319224000.3428.1392718908008@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny closed JBSEAM-5132.
---------------------------------

    Resolution: Done

    
> Two XXE security issues in Seam remoting
> ----------------------------------------
>
>                 Key: JBSEAM-5132
>                 URL: https://issues.jboss.org/browse/JBSEAM-5132
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 2.3.1.Final
>            Reporter: David Jorm
>            Assignee: Marek Novotny
>            Priority: Critical
>             Fix For: 2.3.2.CR1
>
>
> Seam remoting is impacted by 2 XXE security flaws:
> https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6447
> https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6448

--
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

From issues at jboss.org  Wed Feb 26 03:49:47 2014
From: issues at jboss.org (Tomas Remes (JIRA))
Date: Wed, 26 Feb 2014 03:49:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (SEAMVALIDATE-16) Move helloworld
 example to package org.jboss.seam.validation.examples.helloworld
In-Reply-To: <JIRA.12434300.1301552966000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12434300.1301552966000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12434300.1301552966000.22774.1393404587709@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SEAMVALIDATE-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Remes updated SEAMVALIDATE-16:
------------------------------------

        Status: Closed  (was: Pull Request Sent)
    Resolution: Out of Date

    
> Move helloworld example to package org.jboss.seam.validation.examples.helloworld
> --------------------------------------------------------------------------------
>
>                 Key: SEAMVALIDATE-16
>                 URL: https://issues.jboss.org/browse/SEAMVALIDATE-16
>             Project: Seam Validation
>          Issue Type: Task
>    Affects Versions: 3.0.0.Final
>            Reporter: Ondrej Skutka
>            Assignee: Tomas Remes
>            Priority: Minor
>
> Helloworld example doesn't currently reside in it's own package and pollutes org.jboss.seam.validation package. Please move be consistent with the other Seam modules and move it to ...examples.helloworld package.

--
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

From issues at jboss.org  Wed Feb 26 03:53:47 2014
From: issues at jboss.org (Tomas Remes (JIRA))
Date: Wed, 26 Feb 2014 03:53:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5135) Remove old Seam
	ProxyFactory
In-Reply-To: <JIRA.12533322.1393404709318@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533322.1393404709318@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533322.1393404709318.22782.1393404827705@jira02.app.mwc.hst.phx2.redhat.com>

Tomas Remes created JBSEAM-5135:
-----------------------------------

             Summary: Remove old Seam ProxyFactory
                 Key: JBSEAM-5135
                 URL: https://issues.jboss.org/browse/JBSEAM-5135
             Project: Seam 2
          Issue Type: Feature Request
            Reporter: Tomas Remes


org.jboss.seam.util.ProxyFactory can be safely removed from Seam. Purpose of this copy&paste class from Javassist was to correctly handle final methods along with shadow proxies from Drools 4 - you can see https://issues.jboss.org/browse/JBSEAM-1635. 
There are no shadow proxies in Drools 5 and higher, so this class is really useless. 

--
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

From issues at jboss.org  Wed Feb 26 04:51:48 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Wed, 26 Feb 2014 04:51:48 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5135) Remove old Seam
	ProxyFactory
In-Reply-To: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533322.1393404709000.22980.1393408308518@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny reassigned JBSEAM-5135:
-------------------------------------

    Assignee: Marek Novotny

    
> Remove old Seam ProxyFactory
> ----------------------------
>
>                 Key: JBSEAM-5135
>                 URL: https://issues.jboss.org/browse/JBSEAM-5135
>             Project: Seam 2
>          Issue Type: Feature Request
>            Reporter: Tomas Remes
>            Assignee: Marek Novotny
>
> org.jboss.seam.util.ProxyFactory can be safely removed from Seam. Purpose of this copy&paste class from Javassist was to correctly handle final methods along with shadow proxies from Drools 4 - you can see https://issues.jboss.org/browse/JBSEAM-1635. 
> There are no shadow proxies in Drools 5 and higher, so this class is really useless. 

--
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

From issues at jboss.org  Wed Feb 26 04:51:48 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Wed, 26 Feb 2014 04:51:48 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5135) Remove old Seam
	ProxyFactory
In-Reply-To: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533322.1393404709000.22983.1393408308692@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5135:
----------------------------------

    Issue Type: Enhancement  (was: Feature Request)

    
> Remove old Seam ProxyFactory
> ----------------------------
>
>                 Key: JBSEAM-5135
>                 URL: https://issues.jboss.org/browse/JBSEAM-5135
>             Project: Seam 2
>          Issue Type: Enhancement
>            Reporter: Tomas Remes
>            Assignee: Marek Novotny
>
> org.jboss.seam.util.ProxyFactory can be safely removed from Seam. Purpose of this copy&paste class from Javassist was to correctly handle final methods along with shadow proxies from Drools 4 - you can see https://issues.jboss.org/browse/JBSEAM-1635. 
> There are no shadow proxies in Drools 5 and higher, so this class is really useless. 

--
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

From issues at jboss.org  Wed Feb 26 04:51:48 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Wed, 26 Feb 2014 04:51:48 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5135) Remove old Seam
	ProxyFactory
In-Reply-To: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533322.1393404709000.22985.1393408308804@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5135:
----------------------------------

    Fix Version/s: 2.3.2.CR1

    
> Remove old Seam ProxyFactory
> ----------------------------
>
>                 Key: JBSEAM-5135
>                 URL: https://issues.jboss.org/browse/JBSEAM-5135
>             Project: Seam 2
>          Issue Type: Enhancement
>            Reporter: Tomas Remes
>            Assignee: Marek Novotny
>             Fix For: 2.3.2.CR1
>
>
> org.jboss.seam.util.ProxyFactory can be safely removed from Seam. Purpose of this copy&paste class from Javassist was to correctly handle final methods along with shadow proxies from Drools 4 - you can see https://issues.jboss.org/browse/JBSEAM-1635. 
> There are no shadow proxies in Drools 5 and higher, so this class is really useless. 

--
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

From issues at jboss.org  Wed Feb 26 06:39:47 2014
From: issues at jboss.org (Tomas Remes (JIRA))
Date: Wed, 26 Feb 2014 06:39:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5135) Remove old Seam
	ProxyFactory
In-Reply-To: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533322.1393404709000.23465.1393414787940@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Remes updated JBSEAM-5135:
--------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/seam2/jboss-seam/pull/27

    
> Remove old Seam ProxyFactory
> ----------------------------
>
>                 Key: JBSEAM-5135
>                 URL: https://issues.jboss.org/browse/JBSEAM-5135
>             Project: Seam 2
>          Issue Type: Enhancement
>            Reporter: Tomas Remes
>            Assignee: Marek Novotny
>             Fix For: 2.3.2.CR1
>
>
> org.jboss.seam.util.ProxyFactory can be safely removed from Seam. Purpose of this copy&paste class from Javassist was to correctly handle final methods along with shadow proxies from Drools 4 - you can see https://issues.jboss.org/browse/JBSEAM-1635. 
> There are no shadow proxies in Drools 5 and higher, so this class is really useless. 

--
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

From issues at jboss.org  Wed Feb 26 07:37:49 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Wed, 26 Feb 2014 07:37:49 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5135) Remove old Seam
	ProxyFactory
In-Reply-To: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533322.1393404709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533322.1393404709000.23687.1393418269835@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5135:
----------------------------------

        Status: Resolved  (was: Pull Request Sent)
      Assignee: Tomas Remes  (was: Marek Novotny)
    Resolution: Done


merged
                
> Remove old Seam ProxyFactory
> ----------------------------
>
>                 Key: JBSEAM-5135
>                 URL: https://issues.jboss.org/browse/JBSEAM-5135
>             Project: Seam 2
>          Issue Type: Enhancement
>            Reporter: Tomas Remes
>            Assignee: Tomas Remes
>             Fix For: 2.3.2.CR1
>
>
> org.jboss.seam.util.ProxyFactory can be safely removed from Seam. Purpose of this copy&paste class from Javassist was to correctly handle final methods along with shadow proxies from Drools 4 - you can see https://issues.jboss.org/browse/JBSEAM-1635. 
> There are no shadow proxies in Drools 5 and higher, so this class is really useless. 

--
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

From issues at jboss.org  Fri Feb 28 16:45:47 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Fri, 28 Feb 2014 16:45:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5136) EntityConverter should
 allow empty String
In-Reply-To: <JIRA.12533670.1393623941289@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533670.1393623941289@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533670.1393623941289.30608.1393623947599@jira02.app.mwc.hst.phx2.redhat.com>

Marek Novotny created JBSEAM-5136:
-------------------------------------

             Summary: EntityConverter should allow empty String
                 Key: JBSEAM-5136
                 URL: https://issues.jboss.org/browse/JBSEAM-5136
             Project: Seam 2
          Issue Type: Bug
          Components: JSF Integration
    Affects Versions: 2.2.1.CR2
         Environment: seam 2.2.1CR2, PrimeFaces
            Reporter: Cody Lerum
            Assignee: Marek Novotny
             Fix For: 2.2.1.CR3


When using the <s:convertEntity /> tag along with a component such as primefaces autocomplete the EntityConverter will throw a NumberFormatException when it is passed an empty string as JSF is prone to do.

<pf:autoComplete 
       id="fromUserAC" 
       value="#{emailTemplateData.fromUser}"
       widgetVar="fromUserAC" 
       forceSelection="true" 
       completeMethod="#{userLists.searchUsers}" 
       var="_user" 
       itemValue="#{_user}" 
       itemLabel="#{_user.name}" 
       selectListener="#{emailTemplateDataAddUtil.selectFromUser}" 
       onSelectUpdate="fromUser" 
       required="true">
   <s:convertEntity />
</pf:autoComplete>

The solution is to add a .isEmpty() check to the converter.

--
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