[Red Hat JIRA] (WFLY-14143) Can not inject bean from module
by Matěj Novotný (Jira)
[ https://issues.redhat.com/browse/WFLY-14143?page=com.atlassian.jira.plugi... ]
Matěj Novotný closed WFLY-14143.
--------------------------------
Resolution: Not a Bug
> Can not inject bean from module
> -------------------------------
>
> Key: WFLY-14143
> URL: https://issues.redhat.com/browse/WFLY-14143
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Class Loading
> Affects Versions: 21.0.1.Final
> Reporter: Mariusz Kulig
> Assignee: Matěj Novotný
> Priority: Major
> Attachments: mymodule.zip, reproduce_sample.zip
>
>
> Bean from module cannot be injected to bean in deployment. It works properly on Wildfly 20.0.1.Final but does not work on Wildlfy 21.0.1.Final.
> I registered module which contains @ApplicationScoped CDI bean. I tried do deploy WAR archive that contains library that depends on this module. The library contains proper entry in Dependencies section in MANIFEST.MF file.
> I get exception:
>
> {code:java}
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type HelloService with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject com.example.mylib.MyLib.helloService
> at com.example.mylib.MyLib.helloService(MyLib.java:0)
> at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
> {code}
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14143) Can not inject bean from module
by Matěj Novotný (Jira)
[ https://issues.redhat.com/browse/WFLY-14143?page=com.atlassian.jira.plugi... ]
Matěj Novotný reassigned WFLY-14143:
------------------------------------
Assignee: Matěj Novotný (was: Bartosz Baranowski)
> Can not inject bean from module
> -------------------------------
>
> Key: WFLY-14143
> URL: https://issues.redhat.com/browse/WFLY-14143
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Class Loading
> Affects Versions: 21.0.1.Final
> Reporter: Mariusz Kulig
> Assignee: Matěj Novotný
> Priority: Major
> Attachments: mymodule.zip, reproduce_sample.zip
>
>
> Bean from module cannot be injected to bean in deployment. It works properly on Wildfly 20.0.1.Final but does not work on Wildlfy 21.0.1.Final.
> I registered module which contains @ApplicationScoped CDI bean. I tried do deploy WAR archive that contains library that depends on this module. The library contains proper entry in Dependencies section in MANIFEST.MF file.
> I get exception:
>
> {code:java}
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type HelloService with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject com.example.mylib.MyLib.helloService
> at com.example.mylib.MyLib.helloService(MyLib.java:0)
> at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
> {code}
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14143) Can not inject bean from module
by Matěj Novotný (Jira)
[ https://issues.redhat.com/browse/WFLY-14143?page=com.atlassian.jira.plugi... ]
Matěj Novotný commented on WFLY-14143:
--------------------------------------
Hello,
sorry it took me so long to get to this, but other priority items kept popping up.
After testing your reproducer (thanks for that BTW!) I came to a conclusion that this is actually a configuration error, not a bug. Let's first look into how you make it work - the MANIFEST file in your WAR needs to declare the following dependency (mind the meta-inf affix) - {{Dependencies: org.example.mymodule meta-inf}}
This can be achieved via maven war plugin inside your {{MyWar/pom.xml}} in the following way:
{code:java}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>3.2.0</version>
<configuration>
<failOnMissingWebXml>false</failOnMissingWebXml>
<archive>
<manifestEntries>
<Dependencies>org.example.mymodule meta-inf</Dependencies>
</manifestEntries>
</archive>
</configuration>
</plugin>
</plugins>
</build>
{code}
Your JAR (the library) shouldn't need this declaration.
The fact that it worked in earlier versions of WFLY was actually a bug; one that was reported and fixed in WFLY-13641. With this fix in place, all deployments now need to declare that meta-inf dependency if they want to use beans from other deployments (either via MANIFEST or via jboss-deployment-structure).
All of the above is documented here - https://docs.wildfly.org/21/Developer_Guide.html#CDI_Reference
Hope this makes it clear, please ask away if that's not the case.
Meanwhile, I will close this issue as it is not a bug.
> Can not inject bean from module
> -------------------------------
>
> Key: WFLY-14143
> URL: https://issues.redhat.com/browse/WFLY-14143
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Class Loading
> Affects Versions: 21.0.1.Final
> Reporter: Mariusz Kulig
> Assignee: Matěj Novotný
> Priority: Major
> Attachments: mymodule.zip, reproduce_sample.zip
>
>
> Bean from module cannot be injected to bean in deployment. It works properly on Wildfly 20.0.1.Final but does not work on Wildlfy 21.0.1.Final.
> I registered module which contains @ApplicationScoped CDI bean. I tried do deploy WAR archive that contains library that depends on this module. The library contains proper entry in Dependencies section in MANIFEST.MF file.
> I get exception:
>
> {code:java}
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type HelloService with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject com.example.mylib.MyLib.helloService
> at com.example.mylib.MyLib.helloService(MyLib.java:0)
> at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
> {code}
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFWIP-366) MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-366?page=com.atlassian.jira.plugin... ]
Martin Choma updated WFWIP-366:
-------------------------------
Description:
{code}
cd testsuite/integration/microprofile
mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
...
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
[ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
cleanInit=true
overallResponseCode=401
overallSawVendor=false
scopedResponseCode=401
scopedSawVendor=false
expected:<[200]> but was:<[401]>
[INFO]
[ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
{code}
Looking into tested bootable jar It seems strange I still see security-enabled="false"
{code}
<subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
{code}
Management interface is secured
{code}
<management-interfaces>
<http-interface http-authentication-factory="management-http-authentication">
<http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
{code}
But mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
Same test is passing in WF22 nightly runs.
was:
{code}
cd testsuite/integration/microprofile
mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
...
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
[ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
cleanInit=true
overallResponseCode=401
overallSawVendor=false
scopedResponseCode=401
scopedSawVendor=false
expected:<[200]> but was:<[401]>
[INFO]
[ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
{code}
Looking into tested bootable jar It seems strange I still see security-enabled="false"
{code}
<subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
{code}
Management interface is secured
{code}
<management-interfaces>
<http-interface http-authentication-factory="management-http-authentication">
<http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
{code}
and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
> MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-366
> URL: https://issues.redhat.com/browse/WFWIP-366
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> {code}
> cd testsuite/integration/microprofile
> mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
> ...
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
> [ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
> cleanInit=true
> overallResponseCode=401
> overallSawVendor=false
> scopedResponseCode=401
> scopedSawVendor=false
> expected:<[200]> but was:<[401]>
> [INFO]
> [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
> {code}
> Looking into tested bootable jar It seems strange I still see security-enabled="false"
> {code}
> <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
> {code}
> Management interface is secured
> {code}
> <management-interfaces>
> <http-interface http-authentication-factory="management-http-authentication">
> <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> {code}
> But mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
> Same test is passing in WF22 nightly runs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFWIP-366) MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-366?page=com.atlassian.jira.plugin... ]
Martin Choma updated WFWIP-366:
-------------------------------
Description:
{code}
cd testsuite/integration/microprofile
mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
...
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
[ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
cleanInit=true
overallResponseCode=401
overallSawVendor=false
scopedResponseCode=401
scopedSawVendor=false
expected:<[200]> but was:<[401]>
[INFO]
[ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
{code}
Looking into tested bootable jar It seems strange I still see security-enabled="false"
{code}
<subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
{code}
Management interface is secured
{code}
<management-interfaces>
<http-interface http-authentication-factory="management-http-authentication">
<http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
{code}
and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
was:
{code}
cd testsuite/integration/microprofile
mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
...
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
[ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
cleanInit=true
overallResponseCode=401
overallSawVendor=false
scopedResponseCode=401
scopedSawVendor=false
expected:<[200]> but was:<[401]>
[INFO]
[ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
{code}
Looking into tested bootable jar It seems strange I still see security-enabled="false"
{code}
<subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
{code}
and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
> MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-366
> URL: https://issues.redhat.com/browse/WFWIP-366
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> {code}
> cd testsuite/integration/microprofile
> mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
> ...
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
> [ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
> cleanInit=true
> overallResponseCode=401
> overallSawVendor=false
> scopedResponseCode=401
> scopedSawVendor=false
> expected:<[200]> but was:<[401]>
> [INFO]
> [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
> {code}
> Looking into tested bootable jar It seems strange I still see security-enabled="false"
> {code}
> <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
> {code}
> Management interface is secured
> {code}
> <management-interfaces>
> <http-interface http-authentication-factory="management-http-authentication">
> <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/>
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> {code}
> and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFWIP-366) MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFWIP-366?page=com.atlassian.jira.plugin... ]
Martin Choma updated WFWIP-366:
-------------------------------
Description:
{code}
cd testsuite/integration/microprofile
mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
...
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
[ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
cleanInit=true
overallResponseCode=401
overallSawVendor=false
scopedResponseCode=401
scopedSawVendor=false
expected:<[200]> but was:<[401]>
[INFO]
[ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
{code}
Looking into tested bootable jar It seems strange I still see security-enabled="false"
{code}
<subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
{code}
and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
was:
{code}
mvn clean install -B -fae -Dmaven.test.failure.ignore=true -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase
...
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
[ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
cleanInit=true
overallResponseCode=401
overallSawVendor=false
scopedResponseCode=401
scopedSawVendor=false
expected:<[200]> but was:<[401]>
[INFO]
[ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
{code}
Looking into tested bootable jar It seems strange I still see security-enabled="false"
{code}
<subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
{code}
and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
> MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-366
> URL: https://issues.redhat.com/browse/WFWIP-366
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> {code}
> cd testsuite/integration/microprofile
> mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase
> ...
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401>
> [ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true
> cleanInit=true
> overallResponseCode=401
> overallSawVendor=false
> scopedResponseCode=401
> scopedSawVendor=false
> expected:<[200]> but was:<[401]>
> [INFO]
> [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0
> {code}
> Looking into tested bootable jar It seems strange I still see security-enabled="false"
> {code}
> <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
> {code}
> and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (DROOLS-5779) Rule evaluation optimization : alpha node interval index
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5779?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5779:
--------------------------------------
Summary: Rule evaluation optimization : alpha node interval index (was: Rule evaluation optimization : alpha node between range index)
> Rule evaluation optimization : alpha node interval index
> --------------------------------------------------------
>
> Key: DROOLS-5779
> URL: https://issues.redhat.com/browse/DROOLS-5779
> Project: Drools
> Issue Type: Story
> Components: core engine
> Affects Versions: 7.45.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Motivation: This Story aims at alpha node between range indexing which improves performance of between comparison constraints (e.g. age >= 20 && < 30).
> Goals: Better rule execution performance. For each improvement, add benchmark and measure the performance gain.
> Impact: Better rule execution performance. It might have overhead during rule build time. Will confirm with benchmark anyway.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months