April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4984) Enable the executable model in Optaplanner

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4984?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4984: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > Enable the executable model in Optaplanner > ------------------------------------------ > > Key: DROOLS-4984 > URL: https://issues.redhat.com/browse/DROOLS-4984 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Fix For: 7.35.0.Final > > > Currently it's disabled -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5025) Wrong BitMask created by a complex setter argument in modify block

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5025?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5025: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > Wrong BitMask created by a complex setter argument in modify block > ------------------------------------------------------------------ > > Key: DROOLS-5025 > URL: https://issues.redhat.com/browse/DROOLS-5025 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.32.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > With a complex setter argument in modify block like this: > {noformat} > import org.drools.modelcompiler.domain.Person; > rule R > when > $p: Person(address.street == "street1") > then > modify($p) { setLikes( String.valueOf(($p.getAddress().getStreet() + $p.getAddress().getCity()))) }; > end > {noformat} > executable model creates BitMask for "likes" and "address" thus causes a wrong property reactivity behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4891) Further Optimize Lambdas in Executable Model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4891?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4891: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > Further Optimize Lambdas in Executable Model > -------------------------------------------- > > Key: DROOLS-4891 > URL: https://issues.redhat.com/browse/DROOLS-4891 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Labels: good-first-issue > > Lambda shouldn't be externalized depending on the variable name but on the actual lambda. > So > person.name == a > person.name == b > Is effectively the same lambda and should externalized once. > Hint: we could rename the parameters to p1, p2, p3, promote the types to fully qualified names and get this result. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5063) Experimenting with type safe DMN evaluation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5063?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5063: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > Experimenting with type safe DMN evaluation > ------------------------------------------- > > Key: DROOLS-5063 > URL: https://issues.redhat.com/browse/DROOLS-5063 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5101) rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5101?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5101: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError > -------------------------------------------------------------------------- > > Key: DROOLS-5101 > URL: https://issues.redhat.com/browse/DROOLS-5101 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.26.0.Final > Reporter: Charles Herrick > Assignee: Toni Rikkola > Priority: Critical > > 09:13:02,818 ERROR [org.kie.workbench.common.services.backend.builder.core.Builder] (default task-95) GC overhead limit exceeded: java.lang.OutOfMemoryError: GC overhead limit exceeded > 09:13:05,335 ERROR [stderr] (default task-95) java.lang.OutOfMemoryError: GC overhead limit exceeded -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5166) Implement test module for tree model in new PMML implementation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5166?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5166: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > Implement test module for tree model in new PMML implementation > --------------------------------------------------------------- > > Key: DROOLS-5166 > URL: https://issues.redhat.com/browse/DROOLS-5166 > Project: Drools > Issue Type: Task > Reporter: Jiri Petrlik > Assignee: Jiri Petrlik > Priority: Major > Labels: TrustyAI > > Implement test module for PMML tree model in new PMML implementation. This module should contain tests which simultaneously test compiler and evaluator. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5046) [DMN Designer] Marshalling questions

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5046?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5046: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > [DMN Designer] Marshalling questions > ------------------------------------ > > Key: DROOLS-5046 > URL: https://issues.redhat.com/browse/DROOLS-5046 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Michael Anstis > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Our marshaller is EXPLICITLY setting Definitions.typeLanguage to FEEL. Is this acceptable? > DMN1.2 Specification "6.3.2 Definitions metamodel" states : > An instance of Definitions MAY specify a typeLanguage, which is a URI that identifies the default type language used in elements within the scope of this Definitions ... If unspecified, the default typeLanguage is FEEL. > So it is not wrong, but it is not necessary. > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting ItemDefinition.id > DMN1.2 Specification "7.3.2 - ItemDefinition metamodel" states : > ...an instance of ItemDefinition HAS a name and an OPTIONAL id > So it is not wrong, but it is not necessary. > --------------------------------------------------------------------------------- > Our marshaller IS NOT setting ContextEntry.id > DMN1.2 Specification 10.5.2 - ContextEntry metamodel states : > ...ContextEntry is a specialization of DMNElement, from which it INHERITS the OPTIONAL id... > It is therefore correct for us to exclude the id (but _other tools_ includes it. Is that wrong?!) > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting DecisionTable.preferredOrientation (to Rule-as-Row) > DMN1.2 Specification 8.3.1 - Decision Table metamodel states : > ...It has a preferredOrientation, which SHALL be one of the enumerated DecisionTableOrientation. > It is therefore not wrong for us to include preferredOrientation and seems mandatory. > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting inputExpression.id. > DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel:- > ...An instance of InputClause is made of an optional inputExpression... [where an inputExpression is an Expression]. > There is not mention as to whether the Expression inherits its id or needs one explicitly defined. > Is it therefore incorrect for us to include the id? > --------------------------------------------------------------------------------- > Our marshaller IS NOT setting outputEntry.expressionLanguage. > DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel states (well does NOT state anything!) : > OutputClause does not appear to have an expressionLanguage property; only the UnaryTests that is encapsulated by OutputClause supports it. > Is this an issue with _other tools_'s marshaller? > --------------------------------------------------------------------------------- > [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation > https://issues.redhat.com/browse/DROOLS-5045 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4865: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > Add i18n reporting for DMN V&V > ------------------------------ > > Key: DROOLS-4865 > URL: https://issues.redhat.com/browse/DROOLS-4865 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5032) [DMN Designer] Add support for (un)marshalling disconnected connections

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5032: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > [DMN Designer] Add support for (un)marshalling disconnected connections > ----------------------------------------------------------------------- > > Key: DROOLS-5032 > URL: https://issues.redhat.com/browse/DROOLS-5032 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Connections leading 'nowhere' are lost after save and reopen the diagram. > It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node. > The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4575: ----------------------------------- Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23)) > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.redhat.com/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus, drools-tools > > If user opens a scesim file and then close it, no confirmation message should be opened > h2. Manual Acceptance Test > - Opening and closing without changes > - Open, change data in cell, close > - Open, add column, remove column, change column binding, close > - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 April 2020