[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
Chao Wang commented on WFLY-11865:
----------------------------------
10.0.0.Final is no longer maintained. I'd recommend you to try with latest Wildfly 16.0.0.Final.
I don't see any attachment, please provide a runnable reproducer. Thanks
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Chao Wang
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
Chao Wang reassigned WFLY-11865:
--------------------------------
Assignee: Chao Wang (was: Brian Stansberry)
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Chao Wang
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by SHREYAS HOLLA P (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
SHREYAS HOLLA P commented on WFLY-11865:
----------------------------------------
Hi our application works on 10.0.0.Final, upgrading the same to 16.0.0.Final will not be feasible. Please find the attached WAR, which we are deploying on Wildfly deployments. [^cas.war]
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by SHREYAS HOLLA P (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
SHREYAS HOLLA P edited comment on WFLY-11865 at 3/19/19 1:36 AM:
-----------------------------------------------------------------
Hi our application works on 10.0.0.Final, upgrading the same to 16.0.0.Final will not be feasible as there will be dependecies. Please find the attached WAR, which we are deploying on Wildfly deployments. [^cas.war]
was (Author: shreyas.holla):
Hi our application works on 10.0.0.Final, upgrading the same to 16.0.0.Final will not be feasible. Please find the attached WAR, which we are deploying on Wildfly deployments. [^cas.war]
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
Chao Wang commented on WFLY-11865:
----------------------------------
10.0.0.Final was released three years ago, Can you try the latest 16.0.0.Final?
If you see the same problem, Can you share a reproducer?
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by SHREYAS HOLLA P (Jira)
SHREYAS HOLLA P created WFLY-11865:
--------------------------------------
Summary: Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
Key: WFLY-11865
URL: https://issues.jboss.org/browse/WFLY-11865
Project: WildFly
Issue Type: Bug
Reporter: SHREYAS HOLLA P
Assignee: Brian Stansberry
Fix For: 10.0.0.Final
We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11864) Only one JSF Validator is invoked when defined via annotation @FacesValidator
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11864?page=com.atlassian.jira.plugin... ]
Chao Wang moved JBEAP-16571 to WFLY-11864:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11864 (was: JBEAP-16571)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JSF
(was: JSF)
Affects Version/s: 16.0.0.Final
(was: 7.2.0.GA)
(was: 7.3.0.CD15)
Fix Version/s: (was: 7.2.2.GA)
> Only one JSF Validator is invoked when defined via annotation @FacesValidator
> -----------------------------------------------------------------------------
>
> Key: WFLY-11864
> URL: https://issues.jboss.org/browse/WFLY-11864
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 16.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
>
> Only one JSF Validator is invoked when defined via annotation @FacesValidator
> {code}
> @FacesValidator(value = "validator.CustomValidator1", managed = true)
> public class CustomValidator1 implements Validator<String> {
> ...
> }
> @FacesValidator(value = "validator.CustomValidator2", managed = true)
> public class CustomValidator2 implements Validator<String> {
> ...
> }
> {code}
> {code}
> <h:inputText id="input-value" value="#{customBean.inputValue}">
> <f:validator validatorId="validator.CustomValidator2" />
> <f:validator validatorId="validator.CustomValidator1" />
> </h:inputText>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-6918) Unnecessary NoSuchMethodException during JSF app deployment
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-6918?page=com.atlassian.jira.plugin.... ]
Chao Wang commented on WFLY-6918:
---------------------------------
I have opened https://github.com/eclipse-ee4j/mojarra/pull/4545 to address this issue in eclipse-ee4j/mojarra.
> Unnecessary NoSuchMethodException during JSF app deployment
> ------------------------------------------------------------
>
> Key: WFLY-6918
> URL: https://issues.jboss.org/browse/WFLY-6918
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 10.0.0.Final, 10.1.0.CR1
> Environment: it's same at current master
> Reporter: Tomas Remes
> Assignee: Farah Juma
> Priority: Minor
>
> When you turn on TRACE logging for {{javax.enterprise.resource}} then you can notice following exception during JSF app deployment:
> {noformat}
> [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 69) java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider): java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider)
> at java.lang.Class.getConstructor0(Class.java:3082)
> at java.lang.Class.getDeclaredConstructor(Class.java:2178)
> at com.sun.faces.spi.ServiceFactoryUtils.getProviderFromEntry(ServiceFactory.java:83)
> at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:70)
> at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:931)
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:385)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:227)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:200)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:171)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:234)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> Problem is that {{org.jboss.as.jsf.injection.JandexAnnotationProvider}} doesn't have corresponding constructor (with two params - javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months