January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2161) Recursive function definitions in context entries are raising compile time errors

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2161?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2161: ----------------------------------- Sprint: 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 49-50, 2017 Week 51-52) > Recursive function definitions in context entries are raising compile time errors > --------------------------------------------------------------------------------- > > Key: DROOLS-2161 > URL: https://issues.jboss.org/browse/DROOLS-2161 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Edson Tirelli > Assignee: Fedor Gavrilov > Attachments: ContextRecursion.dmn > > > Recursive function definitions in contexts are raising compile time errors but are executing correctly. > See attached model for example. Functions "f" and "h" raise compile time errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2149) Row and column can be added to read only table

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2149?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2149: ----------------------------------- Sprint: 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 49-50, 2017 Week 51-52) > Row and column can be added to read only table > ---------------------------------------------- > > Key: DROOLS-2149 > URL: https://issues.jboss.org/browse/DROOLS-2149 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.6.0.Final > > > The options for adding row or column into guided decision table are not disabled correctly in special case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 (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) > 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)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1795) [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1795: ----------------------------------- Sprint: 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 (was: 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) > [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column. > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1795 > URL: https://issues.jboss.org/browse/DROOLS-1795 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Final > Reporter: Mark Coble > Assignee: Mark Coble > Priority: Minor > Fix For: 7.0.0.Final > > Attachments: guvnor-3507.png > > > If a condition BRL column is added to a DT with bound variables that are used in an action column and that variable name is subsequently changed, the attached error message occurs when updating the action column with the new variable name. In the attached message the original variable name is 'app'. Hitting 'ok' returns you to the DT which has actually refactored the DT with the new variable name and validation is successful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52) > [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)

7 years, 11 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 (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) > 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)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2175) [Guided Decision Table Graph] Refresh after removal of table

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2175?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2175: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 36-37, 2017 Week 49-50, 2017 Week 51-52) > [Guided Decision Table Graph] Refresh after removal of table > ------------------------------------------------------------ > > Key: DROOLS-2175 > URL: https://issues.jboss.org/browse/DROOLS-2175 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.3.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > There are two problem after removal one of linked tables. For more details see Steps to Reproduce. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1959) [DMN Editor] Extend marshaller support for Expressions

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1959?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1959: ----------------------------------- Sprint: 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 (was: 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) > [DMN Editor] Extend marshaller support for Expressions > ------------------------------------------------------ > > Key: DROOLS-1959 > URL: https://issues.jboss.org/browse/DROOLS-1959 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > When UI support for DMN Expression is available, the marshaller shall be extended to support marshalling between DMN xml and the stunner representation of the expression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1946) DMN Editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1946: ----------------------------------- 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 (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) > DMN Editor > ---------- > > Key: DROOLS-1946 > URL: https://issues.jboss.org/browse/DROOLS-1946 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: UX > Fix For: 7.6.0.Final > > > Place holder for all DMN Editor related activities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3484) Nonintuitive error message when for loop is used inside of if/try/batch constructs

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3484?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3484: ---------------------------------------------- You have revealed multiple issues there: 1) Variables can't be set and used inside if/try/for. For example: if (outcome != success) of /system-property=test:read-resource set foo=bar echo $foo ==> You will get an exception. This is the same exception that you are getting when echoing propName 2) There is no check when a redirection is already active and a new redirection is used:e.g.: try followed by if, if followed by if, ... The CLI accepts the new redirection silently. 3) Command name completion is not helpful, although a redirection is active (eg: if), other redirections are proposed (try, for). > Nonintuitive error message when for loop is used inside of if/try/batch constructs > ---------------------------------------------------------------------------------- > > Key: WFCORE-3484 > URL: https://issues.jboss.org/browse/WFCORE-3484 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha5 > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > CLI enables to use for loop construct for looping over commands or operations. See WFCORE-3236 for details. Because of design limitations of CLI, using of for loop is not supported inside of if, try, for and batch constructs. However if you try to do that, error message is not intuitive in all cases and it is difficult to find out why the code does not work. > Let's see on real examples. > {code:title=Using for inside if} > [standalone@embedded /] if (outcome != success) of /system-property=test:read-resource > [standalone@embedded /] for propName in :read-children-names(child-type=system-property) > [standalone@embedded /] echo $propName > Unrecognized variable propName > {code} > As you can see in the example, when you write aforementioned commands into the CLI, no error is thrown until you use the variable declared in the for construct. Additionally the error message is not saying anything about that using of "for" is not allowed inside of "if". > {code:title=Using for inside try} > [standalone@embedded /] try > [standalone@embedded /] for propName in :read-children-names(child-type=system-property) > [standalone@embedded /] echo $propName > Unrecognized variable propName > {code} > The same applies here as for "if" case. > {code:title=Using for inside batch} > [standalone@embedded /] batch > [standalone@embedded / #] for propName in :read-children-names(child-type=system-property) > The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable). > {code} > In the batch case, the error message is better (it says that command is not available), but still it is not clear why the command is not available. > {code:title=Using for inside for} > [standalone@embedded /] for propName in :read-children-names(child-type=system-property) > [standalone@embedded /] for propName in :read-children-names(child-type=system-property) > for is not allowed while in for block > {code} > Using of nested for loops generates nice error message which clearly explains what is wrong. All other cases should throw similar error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018