[JBoss JIRA] (DROOLS-5669) DMN Decision Table Analysis integrated in Maven and Kogito
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5669?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5669:
-----------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> DMN Decision Table Analysis integrated in Maven and Kogito
> ----------------------------------------------------------
>
> Key: DROOLS-5669
> URL: https://issues.redhat.com/browse/DROOLS-5669
> Project: Drools
> Issue Type: Story
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
>
> *Motivation*: currently DT (static) analysis is only available when editor is open
> *Goals*: perform DMN DT analysis during build time, so the user is not required to await when backend services are available, or even worse needed to open DMN files one by one and checking DT analysis manually per each file.
> *Impacts*: integration with kie-maven-plugin, Kogito codegen (which in turn is used by Kogito Quarkus extension AND Kogito maven plugin for SB)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ]
Emmanuel Hugonnet moved WFLY-13909 to WFCORE-5143:
--------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-5143 (was: WFLY-13909)
Affects Version/s: 13.0.0.Beta6
(was: 21.0.0.Beta1)
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFCORE-5143
> URL: https://issues.redhat.com/browse/WFCORE-5143
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 13.0.0.Beta6
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
>
> [~ehugonnet] please set the component. I cannot find anything suitable.
> I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1.
> This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1].
> The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run [2]) but fail against 21.0.0.Beta1, so it is a regression.
> There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list:
> {code}
> org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest
> Error Details
> Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war
> Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}}
> {code}
> *Steps to reproduce*:
> 1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support
> 2. build RESTEasy:
> {code}
> $ mvn install -Dmaven.test.skip=true -Dmaven.repo.local=/home/my-local-repo
> {code}
> 3. cd to testsuite directory:
> {code}
> cd testsuite
> {code}
> 4. run the test against WF 21.0.0.Beta1 with bootable JAR:
> {code}
> mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable
> {code}
> The test should *fail*
> 5. run the test against WF 20.0.1.Final with bootable JAR:
> {code}
> mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable
> {code}
> The test should *pass*
> [1]
> https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46...
> [2]
> https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFLY-13909) Bouncycastle - Failing tests in RESTEasy TS
by Emmanuel Hugonnet (Jira)
Emmanuel Hugonnet created WFLY-13909:
----------------------------------------
Summary: Bouncycastle - Failing tests in RESTEasy TS
Key: WFLY-13909
URL: https://issues.redhat.com/browse/WFLY-13909
Project: WildFly
Issue Type: Bug
Affects Versions: 21.0.0.Beta1
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
[~ehugonnet] please set the component. I cannot find anything suitable.
I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1.
This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1].
The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run [2]) but fail against 21.0.0.Beta1, so it is a regression.
There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list:
{code}
org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest
Error Details
Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war
Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}}
{code}
*Steps to reproduce*:
1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support
2. build RESTEasy:
{code}
$ mvn install -Dmaven.test.skip=true -Dmaven.repo.local=/home/my-local-repo
{code}
3. cd to testsuite directory:
{code}
cd testsuite
{code}
4. run the test against WF 21.0.0.Beta1 with bootable JAR:
{code}
mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable
{code}
The test should *fail*
5. run the test against WF 20.0.1.Final with bootable JAR:
{code}
mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable
{code}
The test should *pass*
[1]
https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46...
[2]
https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-5631) Rule evaluation optimization
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5631?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5631:
-----------------------------------
Sprint: 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28) (was: 2020 Week 37-39 (from Sep 7))
> Rule evaluation optimization
> ----------------------------
>
> Key: DROOLS-5631
> URL: https://issues.redhat.com/browse/DROOLS-5631
> Project: Drools
> Issue Type: Story
> Components: core engine
> Affects Versions: 7.42.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Motivation: This Story aims at rule evaluation optimization so both Kogito and drools core engine usage will get benefits for overall rule execution. It contains Alpha Node Ordering to maximize sharing and minimize the number of evaluations, Range Indexing (I will file and link later). Other JIRAs may be added later.
> 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, 9 months
[JBoss JIRA] (DROOLS-5378) Alpha Node ordering
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5378?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5378:
-----------------------------------
Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28) (was: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7))
> Alpha Node ordering
> -------------------
>
> Key: DROOLS-5378
> URL: https://issues.redhat.com/browse/DROOLS-5378
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 7.38.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Re-order Alpha Node based on some strategies:
> - Expression usage count
> - Other strategies : Chapter 9 "Ordering Conditions" in http://i.stanford.edu/pub/cstr/reports/cs/tr/86/1124/CS-TR-86-1124.pdf
> It would contribute to maximise sharing and minimise the number of evaluations.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-5193) Implement Listener mechanism to trace execution
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5193?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5193:
-----------------------------------
Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7))
> Implement Listener mechanism to trace execution
> -----------------------------------------------
>
> Key: DROOLS-5193
> URL: https://issues.redhat.com/browse/DROOLS-5193
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
>
> Implement Listener architecture so that model-implementation may "publish" execution step detail to be read by "listening" code.
> Implementation should not be mandatory, i.e. model should not be forced to implement it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-5389) Create single abstract class for integration tests in new PMML implementation
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5389?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5389:
-----------------------------------
Sprint: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28) (was: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7))
> Create single abstract class for integration tests in new PMML implementation
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5389
> URL: https://issues.redhat.com/browse/DROOLS-5389
> Project: Drools
> Issue Type: Task
> Reporter: Jiri Petrlik
> Assignee: Jiri Petrlik
> Priority: Major
> Labels: TrustyAI
>
> Currently there are multiple abstract classes for PMML integration tests such as AbstractPMMLTreeTest, AbstractPMMLRegressionTest etc. The goal of this JIRA is to unify them and create one single abstract class.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-5282) Client side FEEL
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5282?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5282:
-----------------------------------
Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7))
> Client side FEEL
> ----------------
>
> Key: DROOLS-5282
> URL: https://issues.redhat.com/browse/DROOLS-5282
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Make kie-dmn-feel usable in the client side.
> Notes:
> * FEEL functions use reflection, but many if not all of them can be hard coded
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months