[JBoss JIRA] (DROOLS-4143) Strange error when generateModel=NO
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4143?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-4143.
---------------------------------
Resolution: Won't Fix
The problem is related with Spark's code generation and independent from Drools. However there's an easy way to fix/workaround this problem that is wrapping the body of the rule's consequence in a static Java method and calling the method from the consequence. Note moreover that this usage pattern that triggers a spark job from a drools consequence is highly discouraged because synchronously stops the rule evaluation until the job isn't finished.
> Strange error when generateModel=NO
> -----------------------------------
>
> Key: DROOLS-4143
> URL: https://issues.jboss.org/browse/DROOLS-4143
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Daniele Zonca
> Assignee: Mario Fusco
> Priority: Major
>
> Reproducer
> https://github.com/danielezonca/tempproject/
> Change in the pom.xml generateModel to NO to have the error
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-4042:
---------------------------------------
[~manstis] I was actually just referring to: when the alias of the import is changed in a DMN import element, update the alias usage within the same DMN model. E.g.:
I click on included models tab, and include ModelX.pmml, then give it the alias "foo".
I create a BKM node in the model that references "foo"
I click on the included models tab, and change the alias from "foo" to "bar".
Can you automatically change the reference in the BKM from "foo" to "bar"?
> [DMN Designer] Add support for importing and consuming PMML models 7.5
> ----------------------------------------------------------------------
>
> Key: DROOLS-4042
> URL: https://issues.jboss.org/browse/DROOLS-4042
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor.
> h2. Requirement
> - As user, via included models tab, remove included pmml model, even if used somewhere
> - As user, via included models tab, rename included pmml model, even if used somewhere
> - As user, via included models tab, include multiple pmml models
> - As user, via included models tab, include multiple pmml models at the same time eternal dmn
> - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished
> - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values
> - As user, via included models tab, no restriction for included pmml model name
> - As user, via new test scenarios, test dmn model that uses pmml inside
> - As user, via kie-server, query kie container that has dmn model with pmml
> - As user, via included models tab, I want to have just unique aliases of imported models
> h2. UX design
> - Selectbox in place of Document and Model selection
> h2. Documentation
> - Mention what pmml model can be imported into dmn
> - Mention where it can be used
> - Mention if something more needed to dpeloy such project on kie server
> h2. Acceptance test
> - Include two pmml models
> - In dmn, select one in function grid
> - Change the selected one to second
> - Finish the dmn model
> - build deploy on kie-server
> - Interact with kie container via rest
> - Create new test scenario for created dmn model
> - In included models tab, try to include one pmml and one dmn with same alias, it shouldn't be possible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-11865:
--------------------------------------
I can't get this application deployed onto WildFly master (18).
{code}
06:44:03,111 INFO [org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker] (ServerService Thread Pool -- 99) Bean 'configurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$996f127b] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
06:44:03,668 ERROR [org.springframework.boot.SpringApplication] (ServerService Thread Pool -- 99) Application startup failed: java.lang.IllegalArgumentException: object is not an instance of declaring class
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.core.io.VfsUtils.invokeVfsMethod(VfsUtils.java:100)
at org.springframework.core.io.VfsUtils.getFile(VfsUtils.java:172)
at org.springframework.core.io.VfsResource.getFile(VfsResource.java:90)
at org.apereo.cas.util.CasVersion.getDateTime(CasVersion.java:59)
at org.apereo.cas.util.SystemUtils.getSystemInfo(SystemUtils.java:50)
at org.apereo.cas.util.spring.boot.AbstractCasBanner.collectEnvironmentInfo(AbstractCasBanner.java:63)
at org.apereo.cas.util.spring.boot.AbstractCasBanner.printBanner(AbstractCasBanner.java:37)
at org.springframework.boot.SpringApplicationBannerPrinter.print(SpringApplicationBannerPrinter.java:71)
at org.springframework.boot.SpringApplication.printBanner(SpringApplication.java:505)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:298)
at org.springframework.boot.web.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:156)
at org.springframework.boot.web.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:136)
at org.springframework.boot.web.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91)
at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:203)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
06:44:03,668 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 99) MSC000001: Failed to start service jboss.deployment.unit."cas.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."cas.war".undertow-deployment: java.lang.RuntimeException: java.lang.IllegalArgumentException: object is not an instance of declaring class
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.lang.RuntimeException: java.lang.IllegalArgumentException: object is not an instance of declaring class
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:252)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
... 8 more
Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.core.io.VfsUtils.invokeVfsMethod(VfsUtils.java:100)
at org.springframework.core.io.VfsUtils.getFile(VfsUtils.java:172)
at org.springframework.core.io.VfsResource.getFile(VfsResource.java:90)
at org.apereo.cas.util.CasVersion.getDateTime(CasVersion.java:59)
at org.apereo.cas.util.SystemUtils.getSystemInfo(SystemUtils.java:50)
at org.apereo.cas.util.spring.boot.AbstractCasBanner.collectEnvironmentInfo(AbstractCasBanner.java:63)
at org.apereo.cas.util.spring.boot.AbstractCasBanner.printBanner(AbstractCasBanner.java:37)
at org.springframework.boot.SpringApplicationBannerPrinter.print(SpringApplicationBannerPrinter.java:71)
at org.springframework.boot.SpringApplication.printBanner(SpringApplication.java:505)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:298)
at org.springframework.boot.web.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:156)
at org.springframework.boot.web.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:136)
at org.springframework.boot.web.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91)
at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:203)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
... 10 more
{code}
I do see several libraries in the {{WEB-INF/lib}} directory that are provided by WildFly. These should likely be removed. I'm not sure if that's the cause of the deployment issue or not.
If I deploy onto WildFly 10.1.0.Final with {{add-logging-api-dependencies}} set to {{false}} it seems to log fine based on the logging subsystem configuration. As discussed on [stackoverflow|https://stackoverflow.com/questions/56045262/wildfly-10-0-0...] there are a lot of dependencies and this would take significant analysis on which dependencies really need to be included and which ones do not.
> 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
> Components: Logging
> Reporter: Shreyas Holla p
> Assignee: James Perkins
> Priority: Major
>
> 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,
> This happens when we add "<add-logging-api-dependencies value="false"/>".
> 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)
6 years, 11 months
[JBoss JIRA] (WFLY-12202) Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm
by Ashley Abdel-Sayed (Jira)
[ https://issues.jboss.org/browse/WFLY-12202?page=com.atlassian.jira.plugin... ]
Ashley Abdel-Sayed reassigned WFLY-12202:
-----------------------------------------
Assignee: Ashley Abdel-Sayed
> Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12202
> URL: https://issues.jboss.org/browse/WFLY-12202
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Reporter: Ashley Abdel-Sayed
> Assignee: Ashley Abdel-Sayed
> Priority: Major
>
> It is requirement to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm .
> --------------------------------------
> <security-domain name="TestDomain" default-realm="TestAggRealm" permission-mapper="default-permission-mapper" pre-realm-principal-transformer="test-transformer" security-event-listener="local-audit">
> <realm name="TestAggRealm" role-decoder="from-roles-attribute"/>
> </security-domain>
> .
> .
> <aggregate-realm name="TestAggRealm" authentication-realm="TestLdapRealm" authorization-realm="Test_Auth_LdapRealm"/>
> --------------------------------------
> I think to achieve this there need to be something like "mid-realm-principal-transformer" in <aggregate-realm> only .
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (ELY-1829) Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm
by Ashley Abdel-Sayed (Jira)
[ https://issues.jboss.org/browse/ELY-1829?page=com.atlassian.jira.plugin.s... ]
Ashley Abdel-Sayed reassigned ELY-1829:
---------------------------------------
Assignee: Ashley Abdel-Sayed
> Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm
> ------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1829
> URL: https://issues.jboss.org/browse/ELY-1829
> Project: WildFly Elytron
> Issue Type: Feature Request
> Reporter: Ashley Abdel-Sayed
> Assignee: Ashley Abdel-Sayed
> Priority: Major
>
> It is requirement to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm .
> --------------------------------------
> <security-domain name="TestDomain" default-realm="TestAggRealm" permission-mapper="default-permission-mapper" pre-realm-principal-transformer="test-transformer" security-event-listener="local-audit">
> <realm name="TestAggRealm" role-decoder="from-roles-attribute"/>
> </security-domain>
> .
> .
> <aggregate-realm name="TestAggRealm" authentication-realm="TestLdapRealm" authorization-realm="Test_Auth_LdapRealm"/>
> --------------------------------------
> I think to achieve this there need to be something like "mid-realm-principal-transformer" in <aggregate-realm> only .
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4496) Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm
by Ashley Abdel-Sayed (Jira)
[ https://issues.jboss.org/browse/WFCORE-4496?page=com.atlassian.jira.plugi... ]
Ashley Abdel-Sayed reassigned WFCORE-4496:
------------------------------------------
Assignee: Ashley Abdel-Sayed
> Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4496
> URL: https://issues.jboss.org/browse/WFCORE-4496
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Indrajit Ingawale
> Assignee: Ashley Abdel-Sayed
> Priority: Major
>
> It is requirement to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm .
> --------------------------------------
> <security-domain name="TestDomain" default-realm="TestAggRealm" permission-mapper="default-permission-mapper" pre-realm-principal-transformer="test-transformer" security-event-listener="local-audit">
> <realm name="TestAggRealm" role-decoder="from-roles-attribute"/>
> </security-domain>
> .
> .
> <aggregate-realm name="TestAggRealm" authentication-realm="TestLdapRealm" authorization-realm="Test_Auth_LdapRealm"/>
> --------------------------------------
> I think to achieve this there need to be something like "mid-realm-principal-transformer" in <aggregate-realm> only .
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11865:
---------------------------------
Fix Version/s: (was: 10.0.0.Final)
> 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
> Components: Logging
> Reporter: Shreyas Holla p
> Assignee: James Perkins
> Priority: Major
>
> 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,
> This happens when we add "<add-logging-api-dependencies value="false"/>".
> 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)
6 years, 11 months