April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2311: ----------------------------------- Sprint: 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > Attachments: Drools-Issue.rar > > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[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, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (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, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > 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.8.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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1480) Support timezones in date and time variables

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1480?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1480: ----------------------------------- Sprint: 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > Support timezones in date and time variables > -------------------------------------------- > > Key: DROOLS-1480 > URL: https://issues.jboss.org/browse/DROOLS-1480 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Beta7 > Reporter: Tibor Zimányi > Assignee: Fedor Gavrilov > Labels: reported-by-qe > > Currently we don't support timezones in date and time variables. This should be implemented, when we are sure about the exact format of timezones. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2180) [Guided Rule Editor] NPE closing a Guided Rule with an incomplete ActionCallMethod

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2180?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2180: ----------------------------------- Sprint: 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 15-16) > [Guided Rule Editor] NPE closing a Guided Rule with an incomplete ActionCallMethod > ---------------------------------------------------------------------------------- > > Key: DROOLS-2180 > URL: https://issues.jboss.org/browse/DROOLS-2180 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Minor > > The implementation of {{ActionCallMethod.hashCode()}} fails if the "method name" is {{null}}. This scenario can arise if you create a new Guided Rule, add a "Call method on..." action and leave it incomplete. Trying to close the editor results in a NPE error (as the "is dirty" mechanism uses {{hashCode()}} implementations). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1701: ----------------------------------- Sprint: 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, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 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, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > FEEL code generation and compilation > ------------------------------------ > > Key: DROOLS-1701 > URL: https://issues.jboss.org/browse/DROOLS-1701 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2156: ----------------------------------- Sprint: 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > DMN decision table names should be presented as titles in editor screen. > ------------------------------------------------------------------------ > > Key: DROOLS-2156 > URL: https://issues.jboss.org/browse/DROOLS-2156 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Labels: UX > > To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[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, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > [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, UXTeam > 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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1609: ----------------------------------- 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, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (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, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > Augment FEEL AST node at compilation with return type > ----------------------------------------------------- > > Key: DROOLS-1609 > URL: https://issues.jboss.org/browse/DROOLS-1609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1954) [DMN Editor] Keyboard shortcuts

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1954?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1954: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 13-14, 2018 Week 15-16) > [DMN Editor] Keyboard shortcuts > ------------------------------- > > Key: DROOLS-1954 > URL: https://issues.jboss.org/browse/DROOLS-1954 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > > The DMN editor could support keyboard shortcuts (similar for current GDT tables) for basic operations like editing of DRD elements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1942) [DMN Editor] InformationItem's "Name" is always the same as the containing node

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1942?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1942: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 13-14, 2018 Week 15-16) > [DMN Editor] InformationItem's "Name" is always the same as the containing node > ------------------------------------------------------------------------------- > > Key: DROOLS-1942 > URL: https://issues.jboss.org/browse/DROOLS-1942 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Whilst an {{InformationItem}} Node has a "Name" its value is always the same as the containing Node's "Name" (for {{InputData}}, {{Decision}} and {{BusinessKnowledgeModel}}). {{ContextEntry}}'s "Name" are not the same as outer most node's "Name" (as a {{ContextEntry}} is contained within a {{Context}} and not directly in a node itself). > It is proposed that this synchronization should be handled in the "Stunner to (org.kie) DMN model" marshalling. Therefore we need to remove the "Name" {{@FormField}} from {{InformationItem}}. > [~tari_manga] [~tirelli] Please confirm. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 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 April 2018