December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4888) spring boot and drools integration occur path error and cannot load rule

by 韩济蓬 (Jira)

韩济蓬 created DROOLS-4888: ---------------------------- Summary: spring boot and drools integration occur path error and cannot load rule Key: DROOLS-4888 URL: https://issues.redhat.com/browse/DROOLS-4888 Project: Drools Issue Type: Bug Components: docs, integration Affects Versions: 7.30.0.Final Reporter: 韩济蓬 Assignee: Mario Fusco I'm trying to run drools 7.30.0.Final with Spring Boot 2.2.2.RELEASE.I configured drools as the documentation says. My drools-config.xml configuration file is where I keep the drools beans and looks like this: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:kie="http://drools.org/schema/kie-spring" xsi:schemaLocation="http://www.springframework.org/schema/beans https://www.springframework.org/schema/beans/spring-beans.xsd http://drools.org/schema/kie-spring http://drools.org/schema/kie-spring.xsd"> <kie:kmodule id="sample_module"> <kie:kbase name="testRules" packages="rules" declarativeAgenda="true"> <kie:ksession name="ksession1" type="stateless"/> <kie:ksession name="ksession2" scope="prototype"> <kie:ruleRuntimeEventListener ref="mockRuleRuntimeEventListener" /> <kie:consoleLogger /> </kie:ksession> </kie:kbase> </kie:kmodule>   <bean class="org.kie.spring.annotations.KModuleAnnotationPostProcessor"/> </beans> {code} occur a warn looks: 2019-12-19 14:44:25.231 WARN 9916 --- [ main] o.d.c.kie.builder.impl.KieProject : No files found for KieBase testRules when i try debug org.kie.spring.KModuleBeanFactoryPostProcessor. Trace to ZipKieModule at line 133. cannot uncompress,get variable urlPath value is "/BOOT-INF/classes" jarFile values is "\Users\user\Desktop\springdrools\target\spring-drools-1.0.jar!\BOOT-INF\classes". lead to cannot load resource. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4887) Rule not fired when modifying a Nested declared type during an incremental update

by Martin Weiler (Jira)

Martin Weiler created DROOLS-4887: ------------------------------------- Summary: Rule not fired when modifying a Nested declared type during an incremental update Key: DROOLS-4887 URL: https://issues.redhat.com/browse/DROOLS-4887 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.31.0.Final Reporter: Martin Weiler Assignee: Mario Fusco When using rules evaluating nested facts, the rule which is supposed to match against the updated (nested) declared type is not fired after an incremental update. The same rule is fired if the KieBase is built from scratch and not updated. See linked PR for a test case. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4886) Rule not fired when modifying a Nested declared type during an incremental update

by Martin Weiler (Jira)

[ https://issues.redhat.com/browse/DROOLS-4886?page=com.atlassian.jira.plug... ] Martin Weiler updated DROOLS-4886: ---------------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/2696 Steps to Reproduce: See https://github.com/kiegroup/drools/pull/2696 > Rule not fired when modifying a Nested declared type during an incremental update > --------------------------------------------------------------------------------- > > Key: DROOLS-4886 > URL: https://issues.redhat.com/browse/DROOLS-4886 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > > When using rules evaluating nested facts, the rule which is supposed to match against the updated (nested) declared type is not fired after an incremental update. The same rule is fired if the KieBase is built from scratch and not updated. See linked PR for a test case. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4886) Rule not fired when modifying a Nested declared type during an incremental update

by Martin Weiler (Jira)

Martin Weiler created DROOLS-4886: ------------------------------------- Summary: Rule not fired when modifying a Nested declared type during an incremental update Key: DROOLS-4886 URL: https://issues.redhat.com/browse/DROOLS-4886 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.31.0.Final Reporter: Martin Weiler Assignee: Mario Fusco When using rules evaluating nested facts, the rule which is supposed to match against the updated (nested) declared type is not fired after an incremental update. The same rule is fired if the KieBase is built from scratch and not updated. See linked PR for a test case. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12888) Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12888?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12888: ------------------------------------ Description: https://github.com/jbossas/el-ri/compare/3.0.3-RELEASE-COMBO...3.0.3.jbos... > Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1 > ------------------------------------------------- > > Key: WFLY-12888 > URL: https://issues.redhat.com/browse/WFLY-12888 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 18.0.1.Final > Reporter: Ilia Vassilev > Assignee: Brian Stansberry > Priority: Major > > https://github.com/jbossas/el-ri/compare/3.0.3-RELEASE-COMBO...3.0.3.jbos... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12888) Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12888?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-12888: --------------------------------------- Assignee: Brian Stansberry (was: Ricardo Martin Camarero) > Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1 > ------------------------------------------------- > > Key: WFLY-12888 > URL: https://issues.redhat.com/browse/WFLY-12888 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 18.0.1.Final > Reporter: Ilia Vassilev > Assignee: Brian Stansberry > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12817) Configuration of Rsyslog in wildfly server

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12817?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-12817. ------------------------------------- Resolution: Explained WildFly supports logging to syslog since the JBoss AS 7.2 days: https://issues.redhat.com/browse/AS7-6298 https://docs.wildfly.org/18/Admin_Guide.html#handlers https://wildscribe.github.io/WildFly/10.0/subsystem/logging/syslog-handle... For help you can try the forum or zulip chat: https://wildfly.org/gethelp/ > Configuration of Rsyslog in wildfly server > ------------------------------------------- > > Key: WFLY-12817 > URL: https://issues.redhat.com/browse/WFLY-12817 > Project: WildFly > Issue Type: Feature Request > Reporter: Meriem MOUNJI > Assignee: Brian Stansberry > Priority: Major > > Hi Guys > Any idea about how to redirect the server.log message to syslog (var/log/messages) in wildfly 10 without using log4j configuration ?!! There is Any other solution For doing That without using Log4j.xml configuration -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12817) Configuration of Rsyslog in wildfly server

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12817?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12817: ------------------------------------ Priority: Major (was: Critical) > Configuration of Rsyslog in wildfly server > ------------------------------------------- > > Key: WFLY-12817 > URL: https://issues.redhat.com/browse/WFLY-12817 > Project: WildFly > Issue Type: Feature Request > Reporter: Meriem MOUNJI > Assignee: Brian Stansberry > Priority: Major > > Hi Guys > Any idea about how to redirect the server.log message to syslog (var/log/messages) in wildfly 10 without using log4j configuration ?!! There is Any other solution For doing That without using Log4j.xml configuration -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12886) WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-12886: --------------------------------------- Component/s: CDI / Weld Assignee: Matěj Novotný (was: Brian Stansberry) > WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-12886 > URL: https://issues.redhat.com/browse/WFLY-12886 > Project: WildFly > Issue Type: Enhancement > Components: CDI / Weld > Affects Versions: 17.0.1.Final > Reporter: nimo stephan > Assignee: Matěj Novotný > Priority: Minor > > I get this info when starting wildfly server: > {code:java} > 01:33:09,168 INFO [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. > {code} > My WebUtils.class imports: > {code:java} > import java.net.URI; > import java.net.http.HttpClient; > import java.net.http.HttpRequest; > import java.net.http.HttpResponse.BodyHandlers; > {code} > Should I include java se module by myself in wildfly to remove this log? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12899) Failing JMXPropertyEditorsTestCase in 18.0.0.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12899?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-12899: ----------------------------------------- [~james-crowley-ibm] The ${env.USER} is just expression syntax meaning "use the value of the environment variable 'USER'". The expression resolution ends up calling System.getEnv("USER"). The test is assuming that env var is set for the server process. AFAIK as long as that property is set for the maven process it ends up being set for the server process. A quick experiment shows the test passes if USER is set to a blank value. If I do this I get the failure you report: $ unset USER $ mvn install -Dts.basic -pl testsuite/integration/basic -Dtest=org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase > Failing JMXPropertyEditorsTestCase in 18.0.0.Final > -------------------------------------------------- > > Key: WFLY-12899 > URL: https://issues.redhat.com/browse/WFLY-12899 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 18.0.0.Final > Reporter: James Crowley > Priority: Major > > When calling "./mvnw install -DallTests", it gets up to the JMXPropertyEditorsTestCase and fails with this error, "Caused by: java.lang.IllegalStateException: Failed to resolve expression: env.USER"}}}}". > Looking at the source code for the test [here|https://github.com/wildfly/wildfly/blob/1bf993be72b570a0c780a58ba05c...], it looks like USER is suppose to be defined by USER_SYS_PROP. > I am not sure what the problem is but I know it is failing somewhere in the above test. > You can see the full log in the in Adopt's test [here|https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1436/conso...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2019