[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1825:
-----------------------------------
Sprint: 2017 Week 45-46, 2017 Week 47-48 (was: 2017 Week 45-46)
> [Guided Decision Table] Ability to change HIT policy in a decision table anytime
> --------------------------------------------------------------------------------
>
> Key: DROOLS-1825
> URL: https://issues.jboss.org/browse/DROOLS-1825
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor
> Affects Versions: 7.1.0.Beta2
> Reporter: Ivo Bek
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: UX
> Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy.
> Thus, it should be possible to change HIT policy in a decision table anytime.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1553) Write documentation for the DMN and FEEL components
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1553?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1553:
-----------------------------------
Sprint: 2017 Week 22-23, 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48 (was: 2017 Week 22-23, 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46)
> Write documentation for the DMN and FEEL components
> ---------------------------------------------------
>
> Key: DROOLS-1553
> URL: https://issues.jboss.org/browse/DROOLS-1553
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Affects Versions: 7.0.0.CR3
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Fix For: 7.5.0.Final
>
>
> Write the documentation for both FEEL and DMN engines.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1597) Implement profile for integration with Signavio's DMN modeler
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1597?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1597:
-----------------------------------
Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46)
> Implement profile for integration with Signavio's DMN modeler
> -------------------------------------------------------------
>
> Key: DROOLS-1597
> URL: https://issues.jboss.org/browse/DROOLS-1597
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Affects Versions: 7.1.0.Beta2
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Fix For: 7.5.0.Final
>
>
> Signavio implements a number of extensions to the DMN standard. As they are a Red Hat partner, we will need to implement a profile in the runtime engine that enables and supports those extensions.
> A short list of extensions is as follows. Details will be added to individual tickets:
> * Support additional FEEL functions and alternate names for existing functions
> * Support the Multi Instance Decision node
> * Support character '?' for interpolation of values in a DT cell
> * Support constraints on List inputs in DT cells
> * Support model composition through BKMs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-2145) Kie-Spring: listeners on KieSession not called when batch is used
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2145?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2145:
-----------------------------------
Sprint: 2017 Week 45-46 (was: BxMS70-Iteration7)
> Kie-Spring: listeners on KieSession not called when batch is used
> -----------------------------------------------------------------
>
> Key: DROOLS-2145
> URL: https://issues.jboss.org/browse/DROOLS-2145
> Project: Drools
> Issue Type: Bug
> Components: integration
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Description of problem:
> When using the following configuration in Spring context, the listener is not called when the rule triggered by the batch fires:
> <kie:ksession name="ksession1">
> <kie:ruleRuntimeEventListener ref="mock-wm-listener"/>
> <kie:batch>
> <kie:insert-object ref="person"/>
> <kie:fire-all-rules/>
> </kie:batch>
> </kie:ksession>
> The listener is triggered when a fact is inserted into the KieSession and fireAllRules() called in the test code (not in the batch).
> The fact seems to be inserted into WM and rules fire when the batch is used. This leads to a suggestion that kie-spring might register listeners after it executes the batch (but I have not verified it).
> Please see PR with unit test for details.
> Version-Release number of selected component (if applicable):
> BRMS 6.2.1
> How reproducible:
> always
> Steps to Reproduce:
> 1. run org.kie.spring.KieSpringListenersBatchTest
> Actual results:
> The test fails.
> Expected results:
> The test succeeds.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-2134) OOPathTest#testDeclarationOutsideOOPath fails with ClassCastException when jitting is enforced
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2134?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2134:
-----------------------------------
Sprint: 2017 Week 45-46 (was: BxMS70-Iteration7)
> OOPathTest#testDeclarationOutsideOOPath fails with ClassCastException when jitting is enforced
> ----------------------------------------------------------------------------------------------
>
> Key: DROOLS-2134
> URL: https://issues.jboss.org/browse/DROOLS-2134
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.4.1.Final
> Reporter: Peter Mačkay
> Assignee: Mario Fusco
> Priority: Minor
> Labels: jitting
>
> When trying to run OOPathTest#testDeclarationOutsideOOPath [1] with enforced jitting, the test fails with following exception:
> {code}
> java.lang.RuntimeException: Error evaluating constraint 'this != $ic1' in []
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:273)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowedCachedLeft(MvelConstraint.java:233)
> at org.drools.core.common.DoubleBetaConstraints.isAllowedCachedLeft(DoubleBetaConstraints.java:109)
> at org.drools.core.phreak.PhreakFromNode.propagate(PhreakFromNode.java:317)
> at org.drools.core.phreak.PhreakFromNode.checkConstraintsAndPropagate(PhreakFromNode.java:290)
> at org.drools.core.phreak.PhreakFromNode.doLeftInserts(PhreakFromNode.java:120)
> at org.drools.core.phreak.PhreakFromNode.doNode(PhreakFromNode.java:68)
> at org.drools.core.phreak.PhreakReactiveFromNode.doNode(PhreakReactiveFromNode.java:34)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:392)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87)
> at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
> at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067)
> at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1320)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1311)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1295)
> at org.drools.compiler.oopath.OOPathTest.testDeclarationOutsideOOPath(OOPathTest.java:1010)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.lang.ClassCastException: org.drools.compiler.oopath.model.TMFile cannot be cast to org.drools.compiler.oopath.model.TMFileSet
> at ConditionEvaluator02d1ed6d278d48e7bf85d6c59d74e5c4.evaluate(Unknown Source)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:271)
> ... 48 more
> {code}
> [1]: https://github.com/kiegroup/drools/blob/6214852d8332b8708bc845794e3f2207c...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months