January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5935) [DMN Designer] Decision Services - The parameters order in the properties panel is not correct

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5935?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5935: ------------------------------------ Story Points: 5 (was: 3) > [DMN Designer] Decision Services - The parameters order in the properties panel is not correct > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-5935 > URL: https://issues.redhat.com/browse/DROOLS-5935 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Critical > Attachments: Screen Shot 2021-01-07 at 18.41.50.png, Screen Shot 2021-01-07 at 18.43.56.png, call centre drd invocation.dmn > > > The parameters order in the properties panel is different from the persisted order. > Here's how the decision service is persisted: > !Screen Shot 2021-01-07 at 18.43.56.png|width=300! > ..and here's how the order of the parameters appear in the component: > !Screen Shot 2021-01-07 at 18.41.50.png|width=500! > And here's the reproducer: [^call centre drd invocation.dmn] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5935) [DMN Designer] Decision Services - The parameters order in the properties panel is not correct

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5935?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5935: ------------------------------------ Tester: Jozef Marko > [DMN Designer] Decision Services - The parameters order in the properties panel is not correct > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-5935 > URL: https://issues.redhat.com/browse/DROOLS-5935 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Critical > Attachments: Screen Shot 2021-01-07 at 18.41.50.png, Screen Shot 2021-01-07 at 18.43.56.png, call centre drd invocation.dmn > > > The parameters order in the properties panel is different from the persisted order. > Here's how the decision service is persisted: > !Screen Shot 2021-01-07 at 18.43.56.png|width=300! > ..and here's how the order of the parameters appear in the component: > !Screen Shot 2021-01-07 at 18.41.50.png|width=500! > And here's the reproducer: [^call centre drd invocation.dmn] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5935) [DMN Designer] Decision Services - The parameters order in the properties panel is not correct

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5935?page=com.atlassian.jira.plug... ] Guilherme Gomes reassigned DROOLS-5935: --------------------------------------- Assignee: Daniel José dos Santos (was: Guilherme Gomes) > [DMN Designer] Decision Services - The parameters order in the properties panel is not correct > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-5935 > URL: https://issues.redhat.com/browse/DROOLS-5935 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Critical > Attachments: Screen Shot 2021-01-07 at 18.41.50.png, Screen Shot 2021-01-07 at 18.43.56.png, call centre drd invocation.dmn > > > The parameters order in the properties panel is different from the persisted order. > Here's how the decision service is persisted: > !Screen Shot 2021-01-07 at 18.43.56.png|width=300! > ..and here's how the order of the parameters appear in the component: > !Screen Shot 2021-01-07 at 18.41.50.png|width=500! > And here's the reproducer: [^call centre drd invocation.dmn] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5935) [DMN Designer] Decision Services - The parameters order in the properties panel is not correct

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-5935: --------------------------------------- Summary: [DMN Designer] Decision Services - The parameters order in the properties panel is not correct Key: DROOLS-5935 URL: https://issues.redhat.com/browse/DROOLS-5935 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Attachments: Screen Shot 2021-01-07 at 18.41.50.png, Screen Shot 2021-01-07 at 18.43.56.png, call centre drd invocation.dmn The parameters order in the properties panel is different from the persisted order. Here's how the decision service is persisted: !Screen Shot 2021-01-07 at 18.43.56.png|width=300! ..and here's how the order of the parameters appear in the component: !Screen Shot 2021-01-07 at 18.41.50.png|width=500! And here's the reproducer: [^call centre drd invocation.dmn] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5216) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set

by Davy Koravand (Jira)

[ https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug... ] Davy Koravand commented on WFCORE-5216: --------------------------------------- Alright, I made it a separate issue as WFCORE-5241. > EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set > ------------------------------------------------------------------------------------- > > Key: WFCORE-5216 > URL: https://issues.redhat.com/browse/WFCORE-5216 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > > Since JBoss EAP 7.3 for OpenShift, if environment variable JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via DeploymentConfig, EAP Pod fails to start with the following messages: > {noformat} > INFO Duration: 347 milliseconds > ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script. > org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297) > at org.jboss.modules.Main.main(Main.java:371) > {noformat} > This issue does not occur on JBoss EAP 7.2 container. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

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

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5788?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5788: ------------------------------------ Summary: [DMN Designer] Show parameters list for Decision Services - Release notes (was: [DMN Designer] Show parameters list for Decision Services - Documentation) > [DMN Designer] Show parameters list for Decision Services - Release notes > ------------------------------------------------------------------------- > > 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)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5241) Jboss-cli issue with spaces in JAVA_OPTS on Unix

by Davy Koravand (Jira)

Davy Koravand created WFCORE-5241: ------------------------------------- Summary: Jboss-cli issue with spaces in JAVA_OPTS on Unix Key: WFCORE-5241 URL: https://issues.redhat.com/browse/WFCORE-5241 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Davy Koravand Assignee: Jean Francois Denise When having spaces in JAVA_OPTS on a Unix machine, calls to jboss-cli.sh will fail (see repro steps for the error). It looks like spaces aren't handled well. It works fine for WF10 but fails on WF21, I'm not sure about the versions in between. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 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: (was: 2020 Week 52-03 (from Dec 21)) > [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)

3 years, 9 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: ------------------------------------ Story Points: 5 (was: 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)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5216) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-5216: ---------------------------------------------- [~davykoravand], I can reproduce your problem with latest wildfly 22 locally built. Actually the fix is different for your issue. You will notice that JAVA_OPTS is not quoted: https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/com... It needs to be quoted, would you mind log a different bug? I would prefer to separate the 2 issues. > EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set > ------------------------------------------------------------------------------------- > > Key: WFCORE-5216 > URL: https://issues.redhat.com/browse/WFCORE-5216 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > > Since JBoss EAP 7.3 for OpenShift, if environment variable JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via DeploymentConfig, EAP Pod fails to start with the following messages: > {noformat} > INFO Duration: 347 milliseconds > ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script. > org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297) > at org.jboss.modules.Main.main(Main.java:371) > {noformat} > This issue does not occur on JBoss EAP 7.2 container. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021