November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1539) Multipart and nested oopath don't work with ruleunit pattern

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1539?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-1539: ---------------------------------- Labels: oopath ruleunits (was: oopath) > Multipart and nested oopath don't work with ruleunit pattern > ------------------------------------------------------------ > > Key: DROOLS-1539 > URL: https://issues.jboss.org/browse/DROOLS-1539 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Labels: oopath, ruleunits > Fix For: 7.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3183) Create unit tests for classes in org.drools.core.ruleunit package

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3183?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-3183: ---------------------------------- Labels: ruleunits (was: ) > Create unit tests for classes in org.drools.core.ruleunit package > ----------------------------------------------------------------- > > Key: DROOLS-3183 > URL: https://issues.jboss.org/browse/DROOLS-3183 > Project: Drools > Issue Type: Story > Components: core engine > Affects Versions: 7.13.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > Priority: Major > Labels: ruleunits > Fix For: 7.14.0.Final > > > We need to have the rule unit classes covered with unit tests, so the coverage is as close to 100% as possible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1533) A RuleUnit is not executed properly when all its DataSources aren't explicitly bound to the executor

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1533?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-1533: ---------------------------------- Labels: ruleunits (was: ) > A RuleUnit is not executed properly when all its DataSources aren't explicitly bound to the executor > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1533 > URL: https://issues.jboss.org/browse/DROOLS-1533 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Labels: ruleunits > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2133) Rule Unit unbind using `run` causes wrong lookup of DS on the wrong unit

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2133?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2133: ---------------------------------- Labels: ruleunits (was: ) > Rule Unit unbind using `run` causes wrong lookup of DS on the wrong unit > ------------------------------------------------------------------------ > > Key: DROOLS-2133 > URL: https://issues.jboss.org/browse/DROOLS-2133 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Matteo Mortari > Assignee: Mario Fusco > Priority: Major > Labels: ruleunits > Fix For: 7.13.0.Final > > > Please reference test {{testGuardAndRunBack}} > {code:java} > public static class MainHouseUnit implements RuleUnit { > private DataSource<Date> now; > private DataSource<String> part; > private DataSource<Boolean> switch1; > public MainHouseUnit() { > super(); > } > public DataSource<Date> getNow() { > return now; > } > public DataSource<String> getPart() { > return part; > } > public DataSource<Boolean> getSwitch1() { > return switch1; > } > } > public static class DayPartUnit implements RuleUnit { > private DataSource<Date> now; > private DataSource<Date> aScopedDS; > private DataSource<String> part; > public DayPartUnit() { > super(); > } > public DataSource<Date> getNow() { > return now; > } > public DataSource<String> getPart() { > return part; > } > public DataSource<Date> getaScopedDS() { > return aScopedDS; > } > } > public static class SwitchUnit implements RuleUnit { > private DataSource<String> part; > private DataSource<Boolean> switch1; > public SwitchUnit() { > super(); > } > public DataSource<String> getPart() { > return part; > } > public DataSource<Boolean> getSwitch1() { > return switch1; > } > } > private KieBase kieBaseMainGuardSubunitRunBackToMain(boolean currentStyle) { > // use "hammer" approach with external multiple call to fire, or "drools.run()" approach in rules. > System.out.println("Running with style: " + currentStyle); > String drl1 = "package org.drools.compiler.integrationtests\n" + > "unit " + getCanonicalSimpleName(MainHouseUnit.class) + "\n" + > "import " + DayPartUnit.class.getCanonicalName() + "\n" + > "import " + SwitchUnit.class.getCanonicalName() + "\n" + > "rule GuardDayPartUnit when\n" + > " Object() from now \n" + > " not( String() from part ) \n" + > "then\n" + > " System.out.println(\"Guarding DayPartUnit\");\n" + > " drools.guard(DayPartUnit.class);\n" + > "end\n" + > "rule GuardSwitchUnit when\n" + > " String() from part \n" + > " not( Boolean() from switch1 ) \n" + > "then\n" + > " System.out.println(\"Guarding SwitchUnit\");\n" + > " drools.guard(SwitchUnit.class);\n" + > "end\n"; > String drl2 = "package org.drools.compiler.integrationtests\n" + > "unit " + getCanonicalSimpleName(DayPartUnit.class) + "\n" + > "import " + MainHouseUnit.class.getCanonicalName() + "\n" + > "rule doDayPartUnit when\n" + > " $n : Object() from now \n" + > "then\n" + > " System.out.println(\"Inside DayPartUnit: \"+$n);\n" + > " part.insert(\"Morning\");\n" + > (currentStyle ? "//" : "") + " drools.run(MainHouseUnit.class);\n" + > "end\n"; > String drl3 = "package org.drools.compiler.integrationtests\n" + > "unit " + getCanonicalSimpleName(SwitchUnit.class) + "\n" + > "import " + MainHouseUnit.class.getCanonicalName() + "\n" + > "rule doSwitchUnit when\n" + > " $n : String() from part \n" + > "then\n" + > " System.out.println(\"Inside SwitchUnit: \"+$n);\n" + > " switch1.insert(true);\n" + > (currentStyle ? "//" : "") + " drools.run(MainHouseUnit.class);\n" + > "end\n"; > KieBase kbase = new KieHelper().addContent(drl1, ResourceType.DRL) > .addContent(drl2, ResourceType.DRL) > .addContent(drl3, ResourceType.DRL) > .build(); > return kbase; > } > @Test > public void testMainGuardSubunitRunBackToMain_usingHammerStyle() throws Exception { > KieBase kbase = kieBaseMainGuardSubunitRunBackToMain(true); > RuleUnitExecutor executor = RuleUnitExecutor.create().bind(kbase); > executor.newDataSource("now", LocalDateTime.now()); > executor.newDataSource("part"); > executor.newDataSource("aScopedDS"); > DataSource<Boolean> switch1 = executor.newDataSource("switch1"); > RuleUnit adultUnit = new MainHouseUnit(); > executor.run(adultUnit); > // need a second, "hammer" run. > executor.run(adultUnit); > assertEquals(true, switch1.iterator().next()); > } > @Test > public void testMainGuardSubunitRunBackToMain_usingRunStyle() throws Exception { > KieBase kbase = kieBaseMainGuardSubunitRunBackToMain(false); > RuleUnitExecutor executor = RuleUnitExecutor.create().bind(kbase); > executor.newDataSource("now", LocalDateTime.now()); > executor.newDataSource("part"); > executor.newDataSource("aScopedDS"); > DataSource<Boolean> switch1 = executor.newDataSource("switch1"); > RuleUnit adultUnit = new MainHouseUnit(); > executor.run(adultUnit); // FAILs with trying to lookup method getaScopedDS() on the MainHouseUnit (which is not correct unit). > // does NOT need a second, "hammer" run. > assertEquals(true, switch1.iterator().next()); > } > public static class EmptyUnit implements RuleUnit { > public EmptyUnit() { > // no-args constructor. > } > } > public static class StringDSUnit implements RuleUnit { > private DataSource<String> strings; > public StringDSUnit() { > // no-args constructor. > } > public DataSource<String> getStrings() { > return strings; > } > } > @Test > public void testGuardAndRunBack() { > String drl1 = "package org.drools.compiler.integrationtests\n" + > "unit " + getCanonicalSimpleName(EmptyUnit.class) + "\n" + > "import " + StringDSUnit.class.getCanonicalName() + "\n" + > "rule RGuard when\n" + > "then\n" + > " System.out.println(\"Guarding StringDSUnit\");\n" + > " drools.guard(StringDSUnit.class);\n" + > "end\n"; > String drl2 = "package org.drools.compiler.integrationtests\n" + > "unit " + getCanonicalSimpleName(StringDSUnit.class) + "\n" + > "import " + EmptyUnit.class.getCanonicalName() + "\n" + > "rule RGoBack when\n" + > "then\n" + > " System.out.println(\"Inside StringDSUnit: \");\n" + > " drools.run(EmptyUnit.class);\n" + > "end\n"; > KieBase kbase = new KieHelper().addContent(drl1, ResourceType.DRL) > .addContent(drl2, ResourceType.DRL) > .build(); > RuleUnitExecutor executor = RuleUnitExecutor.create().bind(kbase); > executor.newDataSource("strings", "abc", "xyz"); > RuleUnit adultUnit = new EmptyUnit(); > executor.run(adultUnit); // FAILs with trying to lookup method getStrings() on the EmptyUnit (which is not correct unit). > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2176) Add ability to use KieRuntimeLogger with RuleUnits

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2176?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2176: ---------------------------------- Labels: ruleunits (was: ) > Add ability to use KieRuntimeLogger with RuleUnits > -------------------------------------------------- > > Key: DROOLS-2176 > URL: https://issues.jboss.org/browse/DROOLS-2176 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Lance Leverich > Assignee: Lance Leverich > Priority: Minor > Labels: ruleunits > Fix For: 7.15.0.Final > > > Need to be able to use the KieRuntimeLogger with RuleUnits, so that the rule debugging can be more effective. > The mechanism for doing this should be exposed via the InternalRuleUnitExecutor interface. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) DMN Editor/Test Scenarios design requirements (dev/UX)

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3126: --------------------------------- Epic Colour: ghx-label-8 (was: ghx-label-4) > DMN Editor/Test Scenarios design requirements (dev/UX) > ------------------------------------------------------ > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam, drools-tools > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) DMN Editor/Test Scenarios design requirements (dev/UX)

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3126: --------------------------------- Epic Colour: ghx-label-10 (was: ghx-label-8) > DMN Editor/Test Scenarios design requirements (dev/UX) > ------------------------------------------------------ > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam, drools-tools > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) DMN Editor/Test Scenarios design requirements (dev/UX)

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3126: --------------------------------- Epic Colour: ghx-label-4 > DMN Editor/Test Scenarios design requirements (dev/UX) > ------------------------------------------------------ > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam, drools-tools > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) DMN Editor/Test Scenarios design requirements (dev/UX)

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3126: --------------------------------- Summary: DMN Editor/Test Scenarios design requirements (dev/UX) (was: Scenario Design Requirements (dev/ux)) > DMN Editor/Test Scenarios design requirements (dev/UX) > ------------------------------------------------------ > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam, drools-tools > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) DMN Editor/Test Scenarios design requirements (dev/UX)

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3126: --------------------------------- Epic Name: DMN Editor/Test Scenarios design requirements (dev/UX) (was: Scenario design requirements (dev/ux)) > DMN Editor/Test Scenarios design requirements (dev/UX) > ------------------------------------------------------ > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam, drools-tools > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018