June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1599) Support Multi Instance Decision node

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1599: ------------------------------------- Summary: Support Multi Instance Decision node Key: DROOLS-1599 URL: https://issues.jboss.org/browse/DROOLS-1599 Project: Drools Issue Type: Sub-task Components: dmn engine Affects Versions: 7.1.0.Beta2 Reporter: Edson Tirelli Assignee: Edson Tirelli Attachments: Screenshot 2017-06-02 19.37.10.png Implement support for Multi Instance Decision node. A multi instance decision node iterates over a list of inputs applying the decision logic to each element. It then combines the results using an aggregation function. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-108) Add README with some basic getting started documentation

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-108?page=com.atlassian.jira.plugi... ] James Perkins reassigned LOGTOOL-108: ------------------------------------- Assignee: James Perkins > Add README with some basic getting started documentation > -------------------------------------------------------- > > Key: LOGTOOL-108 > URL: https://issues.jboss.org/browse/LOGTOOL-108 > Project: Log Tool > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.1.0.Alpha3 > > > There should be a README with some basic getting started tips/how to's. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1598) Support additional FEEL functions and alternate names

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1598: ------------------------------------- Summary: Support additional FEEL functions and alternate names Key: DROOLS-1598 URL: https://issues.jboss.org/browse/DROOLS-1598 Project: Drools Issue Type: Sub-task Components: dmn engine Affects Versions: 7.1.0.Beta2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final Signavio implements a number of additional FEEL functions and also uses alternate names for some functions. The full list can be found here: https://docs.signavio.com/userguide/editor/en/modeling_and_notations/dmn/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1597) Implement profile for integration with Signavio's DMN modeler

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1597: ------------------------------------- Summary: 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.1.0.Final Signavio implement's a number of extensions to the DMN standard. As a Red Hat partner, we will need to implement a profile in the engine that enables and supports those extensions for runtime. 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.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1595) Fix the FEEL "in" operator to work with simple values and variables

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1595?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1595: ------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > Fix the FEEL "in" operator to work with simple values and variables > ------------------------------------------------------------------- > > Key: DROOLS-1595 > URL: https://issues.jboss.org/browse/DROOLS-1595 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > > Currently the "in" operator only works with literal lists or unary tests. Example: > x in [1, 2, 3] > x in >10 > The spec requires the in operator to work with any endpoint, including variables and single values. Example: > x in someList > x in 10 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1568) Improve error messages when using boxed java functions

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1568?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1568: ------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > Improve error messages when using boxed java functions > ------------------------------------------------------ > > Key: DROOLS-1568 > URL: https://issues.jboss.org/browse/DROOLS-1568 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.CR3 > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Fix For: 7.1.0.Final > > > Currently, when the engine does not find the mapped java function (if the user uses an unknown java class or makes a typo in the method signature), it raises an ArrayIndexOutOfBoundsException. > Fix it to properly return a meaningful message to the user, stating the java function was not found. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1596) Error checking allowed values for input nodes of duration and date and time types

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1596?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1596: --------------------------------------- I found two problems here. 1. Period class in Java does not implement Comparable, so it was raising a ClassCastException behind the scenes and swallowing it. Fixed. 2. The input "2017-05-16T17:58Z" is a zoned date and time, so it can't be compared to the local date and time from the ranges. They both have to be zoned, or both have to be local. There was, however no helpful error message before, so I fixed the engine to provide one. It now will show something like this: Error checking allowed values for node 'dateTime': Value '2017-05-16T17:58Z' is not comparable with range '( 2017-05-01T14:03 .. 2017-05-31T14:03 ) > Error checking allowed values for input nodes of duration and date and time types > --------------------------------------------------------------------------------- > > Key: DROOLS-1596 > URL: https://issues.jboss.org/browse/DROOLS-1596 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > Attachments: date_allowed_values.dmn > > > From Melanie: > -------- > Maybe something is off in our serialization, but when I try to execute the attached file it always tell me my values are incorrect event when they are within the allowed range. That file is a really dumb decision that just create a boxed context with the two inputs it gets. Those inputs are one yearMonthDuration and one date time. Both are defined with Item definition and have a constraints on them. Setting constraints on all the other types works fine. > -------- > Here are the messages: > I send P20Y and 2017-05-16T17:58:00.000Z to the back end. Then I use (BuiltInType) BuiltInType.determineTypeFromName(type) in the back end to have the proper feel type and feelType.fromString(value) to get the proper object. > > The returned type for yearMonthDuration is duration and a Period with the proper value is create for it. For date time it is a DATE_TIME and a ZonedDateTime is create for it. > > All of that seem fine. > ---------- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1596) Error checking allowed values for input nodes of duration and date and time types

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1596?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1596: ---------------------------------- Attachment: date_allowed_values.dmn > Error checking allowed values for input nodes of duration and date and time types > --------------------------------------------------------------------------------- > > Key: DROOLS-1596 > URL: https://issues.jboss.org/browse/DROOLS-1596 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > Attachments: date_allowed_values.dmn > > > From Melanie: > -------- > Maybe something is off in our serialization, but when I try to execute the attached file it always tell me my values are incorrect event when they are within the allowed range. That file is a really dumb decision that just create a boxed context with the two inputs it gets. Those inputs are one yearMonthDuration and one date time. Both are defined with Item definition and have a constraints on them. Setting constraints on all the other types works fine. > -------- > Here are the messages: > I send P20Y and 2017-05-16T17:58:00.000Z to the back end. Then I use (BuiltInType) BuiltInType.determineTypeFromName(type) in the back end to have the proper feel type and feelType.fromString(value) to get the proper object. > > The returned type for yearMonthDuration is duration and a Period with the proper value is create for it. For date time it is a DATE_TIME and a ZonedDateTime is create for it. > > All of that seem fine. > ---------- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1596) Error checking allowed values for input nodes of duration and date and time types

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1596?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1596: ---------------------------------- Sprint: 2017 Week 22-23 > Error checking allowed values for input nodes of duration and date and time types > --------------------------------------------------------------------------------- > > Key: DROOLS-1596 > URL: https://issues.jboss.org/browse/DROOLS-1596 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > > From Melanie: > -------- > Maybe something is off in our serialization, but when I try to execute the attached file it always tell me my values are incorrect event when they are within the allowed range. That file is a really dumb decision that just create a boxed context with the two inputs it gets. Those inputs are one yearMonthDuration and one date time. Both are defined with Item definition and have a constraints on them. Setting constraints on all the other types works fine. > -------- > Here are the messages: > I send P20Y and 2017-05-16T17:58:00.000Z to the back end. Then I use (BuiltInType) BuiltInType.determineTypeFromName(type) in the back end to have the proper feel type and feelType.fromString(value) to get the proper object. > > The returned type for yearMonthDuration is duration and a Period with the proper value is create for it. For date time it is a DATE_TIME and a ZonedDateTime is create for it. > > All of that seem fine. > ---------- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1596) Error checking allowed values for input nodes of duration and date and time types

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1596: ------------------------------------- Summary: Error checking allowed values for input nodes of duration and date and time types Key: DROOLS-1596 URL: https://issues.jboss.org/browse/DROOLS-1596 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.1.0.Beta2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final >From Melanie: -------- Maybe something is off in our serialization, but when I try to execute the attached file it always tell me my values are incorrect event when they are within the allowed range. That file is a really dumb decision that just create a boxed context with the two inputs it gets. Those inputs are one yearMonthDuration and one date time. Both are defined with Item definition and have a constraints on them. Setting constraints on all the other types works fine. -------- Here are the messages: I send P20Y and 2017-05-16T17:58:00.000Z to the back end. Then I use (BuiltInType) BuiltInType.determineTypeFromName(type) in the back end to have the proper feel type and feelType.fromString(value) to get the proper object. The returned type for yearMonthDuration is duration and a Period with the proper value is create for it. For date time it is a DATE_TIME and a ZonedDateTime is create for it. All of that seem fine. ---------- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017