January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-4771) Fix validation for background/wrong dmn scesim files

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4771?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4771: -------------------------------- Component/s: Scenario Simulation and Testing > Fix validation for background/wrong dmn scesim files > ---------------------------------------------------- > > Key: DROOLS-4771 > URL: https://issues.redhat.com/browse/DROOLS-4771 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > > Validation should be enabled also for background data. > Beside that, when importing a scesim file related to a missing dmn, the validation on import should fail (currently is does not) -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-11953) Define Galleon Layer for ejb3

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-11953?page=com.atlassian.jira.plugi... ] Jean Francois Denise closed WFLY-11953. --------------------------------------- Resolution: Duplicate Issue This has been fixed by WFLY-13354 > Define Galleon Layer for ejb3 > ----------------------------- > > Key: WFLY-11953 > URL: https://issues.redhat.com/browse/WFLY-11953 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > There is a need to compose a custom server with ejb3. > https://developer.jboss.org/thread/279916 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5750) [DMN Designer] Decision Service is missing inputData element in model with multiple DRDs

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5750?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5750: ------------------------------------ Sprint: 2020 Week 52-03 (from Dec 21) Story Points: 3 > [DMN Designer] Decision Service is missing inputData element in model with multiple DRDs > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5750 > URL: https://issues.redhat.com/browse/DROOLS-5750 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.46.0.Final > Reporter: Jan Stastny > Assignee: Guilherme Gomes > Priority: Major > Attachments: call centre drd.dmn > > > When model has multiple DRDs and tries to reuse a decision component by adding it into a Decision Service node, the resulting Decision Service node has no *inputData* definitions. > In multiple DRDs models the ultimate decision components representation should reflect all the relations merged from their occurrences - i.e. in this case it should not matter that the Input is not defined directly in the DRD with the Decision Service. The Decision Service should inherit the inputData elements based on what inputs do the included decisions have. > See [^call centre drd.dmn] . > That's a multiple DRD model with Decision Service *office accepts the call* which suffers from this issue, in the file the fix is already applied - by adding the > {code:xml} > <dmn:inputData href="#_4208DF15-2342-46EA-8EFF-E402FDDC2F5E"/> > {code} > so that the resulting decisionService definition is > {code:xml} > <dmn:decisionService id="_D36C61E4-C5DB-4375-855B-D58A0269A570" name="office accepts the call"> > <dmn:extensionElements/> > <dmn:variable id="_EDEE0B3D-2B82-4FDE-B725-4ECFBE8F8768" name="office accepts the call" typeRef="boolean"/> > <dmn:outputDecision href="#_25C72B4D-63EF-406F-89C6-612B2090E984"/> > <dmn:encapsulatedDecision href="#_4F791054-DEBD-4EA7-95BA-9E4695239822"/> > <dmn:encapsulatedDecision href="#_606C3BEC-097B-4DA4-9209-9BBA72EBCEF1"/> > <dmn:inputData href="#_4208DF15-2342-46EA-8EFF-E402FDDC2F5E"/> > </dmn:decisionService> > {code} > When the decision endpoint is invoked (before applying the workaround) the evaluation fails and log contains following: > {code} > ERROR [org.kie.dmn.core.ast.DMNDecisionServiceFunctionDefinitionEvaluator] (default task-35) Parameter count mismatch invoking decision service function 'office accepts the call' > {code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5788) [DMN Designer] Show parameters list for Decision Services - Documentation

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5788?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5788: ------------------------------------ Sprint: 2020 Week 52-03 (from Dec 21) Story Points: 1 > [DMN Designer] Show parameters list for Decision Services - Documentation > ------------------------------------------------------------------------- > > Key: DROOLS-5788 > URL: https://issues.redhat.com/browse/DROOLS-5788 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > > Add a release notes entry on BC release notes and Kogito release notes about this feature. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5787) [DMN Designer] Show parameters list for Decision Services - Blog post

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5787?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5787: ------------------------------------ Sprint: 2020 Week 52-03 (from Dec 21) Story Points: 1 > [DMN Designer] Show parameters list for Decision Services - Blog post > --------------------------------------------------------------------- > > Key: DROOLS-5787 > URL: https://issues.redhat.com/browse/DROOLS-5787 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > > Blog post on http://blog.kie.org about this feature. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14271) NullPointerException when ejb timers services fails during loading timer from database upon activation

by Enrique González Martínez (Jira)

[ https://issues.redhat.com/browse/WFLY-14271?page=com.atlassian.jira.plugi... ] Enrique González Martínez reassigned WFLY-14271: ------------------------------------------------ Assignee: Enrique González Martínez (was: Brian Stansberry) > NullPointerException when ejb timers services fails during loading timer from database upon activation > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-14271 > URL: https://issues.redhat.com/browse/WFLY-14271 > Project: WildFly > Issue Type: Bug > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Priority: Major > > NullPointerException when ejb timers services fails during loading timer from database upon activation. > > This causes the timerObjectId set not being created and failing afterwards. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14271) NullPointerException when ejb timers services fails during loading timer from database upon activation

by Enrique González Martínez (Jira)

Enrique González Martínez created WFLY-14271: ------------------------------------------------ Summary: NullPointerException when ejb timers services fails during loading timer from database upon activation Key: WFLY-14271 URL: https://issues.redhat.com/browse/WFLY-14271 Project: WildFly Issue Type: Bug Reporter: Enrique González Martínez Assignee: Brian Stansberry NullPointerException when ejb timers services fails during loading timer from database upon activation. This causes the timerObjectId set not being created and failing afterwards. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1258) Introduce process for checking installed images on cluster before testing

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1258: ------------------------------------ Summary: Introduce process for checking installed images on cluster before testing Key: SWSQE-1258 URL: https://issues.redhat.com/browse/SWSQE-1258 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta We need to avoid a problem with testing different images than expected. Before each testing, we need to check ideally automatically that the cluster contains expected images. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5913) [DMN Designer] Improving UX when Decision Table is relying on not updated data.

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5913?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5913: -------------------------------- Labels: Field Support (was: ) > [DMN Designer] Improving UX when Decision Table is relying on not updated data. > -------------------------------------------------------------------------------- > > Key: DROOLS-5913 > URL: https://issues.redhat.com/browse/DROOLS-5913 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Yeser Amer > Assignee: Guilherme Gomes > Priority: Major > Labels: Field, Support > > We should find a way to improve User Experience in the case a Decision Table is relying on Data Type which was modified by the user. > Original Message: > {noformat} > TL;DR a modification of an Object (aka Structure) in the Data Model does not get reflected in the DMN Model. > Maybe someone can point out the error in the following scenario. > (1) Using the DMN editor in BC RHPAM.7.9 I defined the "Ve" Object (aka Structure) and the "Ve_data1" simple variable in the Data Model as custom data types > (2) "Ve", named as "Vehicle", was used as data input to a DMN model and a decision was defined backed by a decision table > (3) when the decision table was first created the columns for the "Vehicle" attributes were created as individual columns. > (4) Modified the "Ve" structure by removing some attributes > (5) The deleted attributes are still available in the decision table. > I have two issues in this scenario. > (I1) Step (3). By creating the columns as individual columns of the "Vehicle" variable in the decision table any sense between them belonging to the "Ve" structure is lost. Furthermore the decision table allows for changing the data type of the columns despite the fact that these belong(?) to the "Ve" object. > (I2) Step (5). I was expecting that by modifying the columns in the data structure that change would be visible in the decision table as well. Yes, a warning is generated, but it is cryptic, lost in a table full of equally cryptic messages and no visual indication of the actual problem in the decision table. I can check the messages and find out what is going on, but explaining this to my customer proved to be quite a challenge. > We are still targeting DMN to business analysts I presume. > {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5913) [DMN Designer] Improving UX when Decision Table is relying on not updated data.

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5913?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5913: -------------------------------- Component/s: DMN Editor Tester: Jozef Marko > [DMN Designer] Improving UX when Decision Table is relying on not updated data. > -------------------------------------------------------------------------------- > > Key: DROOLS-5913 > URL: https://issues.redhat.com/browse/DROOLS-5913 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Yeser Amer > Assignee: Guilherme Gomes > Priority: Major > > We should find a way to improve User Experience in the case a Decision Table is relying on Data Type which was modified by the user. > Original Message: > {noformat} > TL;DR a modification of an Object (aka Structure) in the Data Model does not get reflected in the DMN Model. > Maybe someone can point out the error in the following scenario. > (1) Using the DMN editor in BC RHPAM.7.9 I defined the "Ve" Object (aka Structure) and the "Ve_data1" simple variable in the Data Model as custom data types > (2) "Ve", named as "Vehicle", was used as data input to a DMN model and a decision was defined backed by a decision table > (3) when the decision table was first created the columns for the "Vehicle" attributes were created as individual columns. > (4) Modified the "Ve" structure by removing some attributes > (5) The deleted attributes are still available in the decision table. > I have two issues in this scenario. > (I1) Step (3). By creating the columns as individual columns of the "Vehicle" variable in the decision table any sense between them belonging to the "Ve" structure is lost. Furthermore the decision table allows for changing the data type of the columns despite the fact that these belong(?) to the "Ve" object. > (I2) Step (5). I was expecting that by modifying the columns in the data structure that change would be visible in the decision table as well. Yes, a warning is generated, but it is cryptic, lost in a table full of equally cryptic messages and no visual indication of the actual problem in the decision table. I can check the messages and find out what is going on, but explaining this to my customer proved to be quite a challenge. > We are still targeting DMN to business analysts I presume. > {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 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 January 2021