May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4020) [DMN Designer] Literal expression variable name is missing

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4020?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4020: -------------------------------- Priority: Blocker (was: Major) > [DMN Designer] Literal expression variable name is missing > ---------------------------------------------------------- > > Key: DROOLS-4020 > URL: https://issues.jboss.org/browse/DROOLS-4020 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Attachments: Screenshot from 2019-05-15 10-56-00.png, curl_command.sh, screenshot-1.png, tournament.zip > > > There seems to be issue if user wants to store the result of imported logic. In the attached artificial project there is *nhl.dmn* model. This model works just with constants, no input nodes. This model produces two matches (*first_match* and *second_match*) of NHL. In both cases *team a* is a constant and *team b* is also constant but from other node. > The *first_match* seems working correctly while the *second_match* doesn't. The only difference is the *second_match* node uses value from imported node. See the steps to reproduce. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4020) [DMN Designer] Literal expression variable name is missing

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4020?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4020: -------------------------------- Component/s: DMN Editor (was: dmn engine) > [DMN Designer] Literal expression variable name is missing > ---------------------------------------------------------- > > Key: DROOLS-4020 > URL: https://issues.jboss.org/browse/DROOLS-4020 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Attachments: Screenshot from 2019-05-15 10-56-00.png, curl_command.sh, screenshot-1.png, tournament.zip > > > There seems to be issue if user wants to store the result of imported logic. In the attached artificial project there is *nhl.dmn* model. This model works just with constants, no input nodes. This model produces two matches (*first_match* and *second_match*) of NHL. In both cases *team a* is a constant and *team b* is also constant but from other node. > The *first_match* seems working correctly while the *second_match* doesn't. The only difference is the *second_match* node uses value from imported node. See the steps to reproduce. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4020) [DMN Designer] Literal expression variable name is missing

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4020?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4020: -------------------------------- Attachment: Screenshot from 2019-05-15 10-56-00.png > [DMN Designer] Literal expression variable name is missing > ---------------------------------------------------------- > > Key: DROOLS-4020 > URL: https://issues.jboss.org/browse/DROOLS-4020 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Attachments: Screenshot from 2019-05-15 10-56-00.png, curl_command.sh, screenshot-1.png, tournament.zip > > > There seems to be issue if user wants to store the result of imported logic. In the attached artificial project there is *nhl.dmn* model. This model works just with constants, no input nodes. This model produces two matches (*first_match* and *second_match*) of NHL. In both cases *team a* is a constant and *team b* is also constant but from other node. > The *first_match* seems working correctly while the *second_match* doesn't. The only difference is the *second_match* node uses value from imported node. See the steps to reproduce. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4020) [DMN Designer] Literal expression variable name is missing

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4020?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4020: -------------------------------- Summary: [DMN Designer] Literal expression variable name is missing (was: DMN Invocation of imported logic is not stored) > [DMN Designer] Literal expression variable name is missing > ---------------------------------------------------------- > > Key: DROOLS-4020 > URL: https://issues.jboss.org/browse/DROOLS-4020 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Priority: Major > Attachments: Screenshot from 2019-05-15 10-56-00.png, curl_command.sh, screenshot-1.png, tournament.zip > > > There seems to be issue if user wants to store the result of imported logic. In the attached artificial project there is *nhl.dmn* model. This model works just with constants, no input nodes. This model produces two matches (*first_match* and *second_match*) of NHL. In both cases *team a* is a constant and *team b* is also constant but from other node. > The *first_match* seems working correctly while the *second_match* doesn't. The only difference is the *second_match* node uses value from imported node. See the steps to reproduce. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4020) [DMN Designer] Literal expression variable name is missing

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4020?page=com.atlassian.jira.plugi... ] Jozef Marko reassigned DROOLS-4020: ----------------------------------- Assignee: Michael Anstis (was: Matteo Mortari) > [DMN Designer] Literal expression variable name is missing > ---------------------------------------------------------- > > Key: DROOLS-4020 > URL: https://issues.jboss.org/browse/DROOLS-4020 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Attachments: Screenshot from 2019-05-15 10-56-00.png, curl_command.sh, screenshot-1.png, tournament.zip > > > There seems to be issue if user wants to store the result of imported logic. In the attached artificial project there is *nhl.dmn* model. This model works just with constants, no input nodes. This model produces two matches (*first_match* and *second_match*) of NHL. In both cases *team a* is a constant and *team b* is also constant but from other node. > The *first_match* seems working correctly while the *second_match* doesn't. The only difference is the *second_match* node uses value from imported node. See the steps to reproduce. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4029) Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4029?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4029: ----------------------------------- Sprint: 2019 Week 20-22 > Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler > -------------------------------------------------------------------------------------- > > Key: DROOLS-4029 > URL: https://issues.jboss.org/browse/DROOLS-4029 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > Quarkus core hot code reload is assuming that the compiled class file for "Foo.ext" is always "Foo.class", whatever is the ext, whatever the contents. > This is false for DRL, BPMN but it is also false for java. Consider the case: > {code} > /* package-private */ class Blah {} > {code} > which always generates {{{Blah.class}} regardless of the java file name. > see https://github.com/quarkusio/quarkus/issues/2371 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4027) Test Scenario: improve the DMN asset selection experience

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4027?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-4027. ------------------------------------ Resolution: Duplicate Issue > Test Scenario: improve the DMN asset selection experience > --------------------------------------------------------- > > Key: DROOLS-4027 > URL: https://issues.jboss.org/browse/DROOLS-4027 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.21.0.Final > Environment: Create a new Test Scenario for DMN > Reporter: Donato Marrazzo > Assignee: Gabriele Cardosi > Priority: Minor > Labels: Field, drools-tools > Attachments: Screenshot from 2019-05-15 06-35-52.png > > > When a user creates a new Test Scenario for DMN, he has to choose the DMN asset: > !Screenshot from 2019-05-15 06-35-52.png! > The asset is presented with the full physical path, which is a bit confusing even because it does not fit the field length. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4027) Test Scenario: improve the DMN asset selection experience

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4027?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4027: ----------------------------------- Component/s: Scenario Simulation and Testing (was: DMN Editor) > Test Scenario: improve the DMN asset selection experience > --------------------------------------------------------- > > Key: DROOLS-4027 > URL: https://issues.jboss.org/browse/DROOLS-4027 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.21.0.Final > Environment: Create a new Test Scenario for DMN > Reporter: Donato Marrazzo > Assignee: Gabriele Cardosi > Priority: Minor > Labels: Field, drools-tools > Attachments: Screenshot from 2019-05-15 06-35-52.png > > > When a user creates a new Test Scenario for DMN, he has to choose the DMN asset: > !Screenshot from 2019-05-15 06-35-52.png! > The asset is presented with the full physical path, which is a bit confusing even because it does not fit the field length. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4029) Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4029?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4029: ----------------------------------- Description: Quarkus core hot code reload is assuming that the compiled class file for "Foo.ext" is always "Foo.class", whatever is the ext, whatever the contents. This is false for DRL, BPMN but it is also false for java. Consider the case: {code} /* package-private */ class Blah {} {code} which always generates {{{Blah.class}} regardless of the java file name. see https://github.com/quarkusio/quarkus/issues/2371 was: Quarkus core is limited, as it does not support file watches outside src/main/java. We need to watch src/main/resources, so we have to patch core to support extra "source" directories. see https://github.com/quarkusio/quarkus/issues/2370 > Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler > -------------------------------------------------------------------------------------- > > Key: DROOLS-4029 > URL: https://issues.jboss.org/browse/DROOLS-4029 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > Quarkus core hot code reload is assuming that the compiled class file for "Foo.ext" is always "Foo.class", whatever is the ext, whatever the contents. > This is false for DRL, BPMN but it is also false for java. Consider the case: > {code} > /* package-private */ class Blah {} > {code} > which always generates {{{Blah.class}} regardless of the java file name. > see https://github.com/quarkusio/quarkus/issues/2371 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4029) Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4029?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4029: ----------------------------------- Git Pull Request: https://github.com/quarkusio/quarkus/pull/2443 (was: https://github.com/quarkusio/quarkus/pull/2439) > Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler > -------------------------------------------------------------------------------------- > > Key: DROOLS-4029 > URL: https://issues.jboss.org/browse/DROOLS-4029 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > Quarkus core hot code reload is assuming that the compiled class file for "Foo.ext" is always "Foo.class", whatever is the ext, whatever the contents. > This is false for DRL, BPMN but it is also false for java. Consider the case: > {code} > /* package-private */ class Blah {} > {code} > which always generates {{{Blah.class}} regardless of the java file name. > see https://github.com/quarkusio/quarkus/issues/2371 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019