September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5612) DMN integrate test example from DMN spec not listed in ADOC

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5612?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5612: ----------------------------------- Sprint: 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2020 Week 34-36 (from Aug 17)) > DMN integrate test example from DMN spec not listed in ADOC > ----------------------------------------------------------- > > Key: DROOLS-5612 > URL: https://issues.redhat.com/browse/DROOLS-5612 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Follows up [BXMSDOC-6058] and [DROOLS-5440] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4606) DMN alpha network POC

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4606?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4606: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17)) > DMN alpha network POC > --------------------- > > Key: DROOLS-4606 > URL: https://issues.redhat.com/browse/DROOLS-4606 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > > Start refactoring work to support alpha network -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[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) (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)) > 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)

4 years, 3 months

1
0
0 / 0

[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) (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)) > 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)

4 years, 3 months

1
0
0 / 0

[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) (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)) > 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)

4 years, 3 months

1
0
0 / 0

[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) (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)) > 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)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4461?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4461: ----------------------------------- Sprint: 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) (was: 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)) > Use date picker for LocalDate > ----------------------------- > > Key: DROOLS-4461 > URL: https://issues.redhat.com/browse/DROOLS-4461 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > We should use the date picker for LocalDate like we do for Date. > h2. Acceptance test > - Guided rule condition (/) > - Guided rule action (/) > - Guided rule template condition (/) > - Guided rule template action (/) > - Guided decision table simple condition (/) > - Guided decision table BRL condition (/) > - Guided decision table simple action (/) > - Guided decision table BRL action (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4367) Tests in drools coverage are not really using the executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4367?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4367: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 34-36 (from Aug 17)) > Tests in drools coverage are not really using the executable model > ------------------------------------------------------------------ > > Key: DROOLS-4367 > URL: https://issues.redhat.com/browse/DROOLS-4367 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Daniel Rosa > Priority: Minor > > Such as > https://github.com/kiegroup/drools/blob/ba9c79c4bfaf9cfc1ec2363bee3865c3d... > Even if the test itself is parametrized, in the body it calls directly buildAll therefore discarding the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5608) Cannot use method chaining as source for facts

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5608?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5608: ----------------------------------- Sprint: 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2020 Week 34-36 (from Aug 17)) > Cannot use method chaining as source for facts > ---------------------------------------------- > > Key: DROOLS-5608 > URL: https://issues.redhat.com/browse/DROOLS-5608 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.42.0.Final > Reporter: Ciprian Chiru > Assignee: Luca Molteni > Priority: Major > > Given the sample rule below: > {code:java} > import java.util.*; > global java.util.Set controlSet; > rule "will execute per each Measurement having ID color" > no-loop > when > Measurement( id == "color", $colorVal : val ) > String() from Optional.of($colorVal).orElse("blah") > then > controlSet.add($colorVal); > end{code} > > Compiling the resulting model fails with: > {code:java} > .../target/generated-sources/drools-model-compiler/main/java/rules/Rules79f20b1c9ba841128eaf4b2dbb336819RuleMethods0.java:[24,129] cannot find symbol > [ERROR] symbol: variable $colorVal > [ERROR] location: class rules.Rules79f20b1c9ba841128eaf4b2dbb336819RuleMethods0{code} > Can be reproduced with _7.43.0-SNAPSHOT_ > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5486) CEP doesn't evaluate correctly when a bind variable is used as the first temporal parameter in executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5486?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5486: ----------------------------------- Sprint: 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) (was: 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17)) > CEP doesn't evaluate correctly when a bind variable is used as the first temporal parameter in executable model > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5486 > URL: https://issues.redhat.com/browse/DROOLS-5486 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.39.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > With the below test, standard-drl fires but executable-model doesn't. > {code:java} > @Test > public void testAfterOnLongFields2() throws Exception { > String str = > "import " + StockTick.class.getCanonicalName() + ";\n" + > "declare StockTick @timestamp(timeFieldAsLong) end\n" + > "rule R when\n" + > " $a : StockTick( company == \"DROO\" )\n" + > " $b : StockTick( company == \"ACME\", $a.timeFieldAsLong after[5,8] timeFieldAsLong )\n" + > "then\n" + > " System.out.println(\"fired\");\n" + > "end\n"; > KieSession ksession = getKieSession(getCepKieModuleModel(), str); > SessionPseudoClock clock = ksession.getSessionClock(); > > ReteDumper.dumpRete(ksession); > ksession.insert( new StockTick( "ACME" ).setTimeField( 0 ) ); > ksession.insert( new StockTick( "DROO" ).setTimeField( 6 ) ); > assertEquals( 1, ksession.fireAllRules() ); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020