April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5255) [Guided Decision Table] fields are listed twice

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5255?page=com.atlassian.jira.plug... ] Jozef Marko moved RHDM-1319 to DROOLS-5255: ------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-5255 (was: RHDM-1319) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Guided Decision Table Editor (was: Decision Central) Affects Build: (was: CR1) Affects Version/s: 7.37.0.Final (was: 7.7.0.GA) QE Status: NEW > [Guided Decision Table] fields are listed twice > ----------------------------------------------- > > Key: DROOLS-5255 > URL: https://issues.redhat.com/browse/DROOLS-5255 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.37.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: Regression, drools-tools > Attachments: Screenshot from 2020-02-18 12-15-41.png > > > There is an issue if dialog for inserting condition column into guided decision table is shown first time. In such case available fields for constraint are listed twice, see the attached screenshot and steps to reproduce. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2466) add isTraceEnabled() when log.trace

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2466?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2466: -------------------------------- These methods are not called frequently, therefore I don't think an {{if(if_trace)}} is needed. > add isTraceEnabled() when log.trace > ----------------------------------- > > Key: JGRP-2466 > URL: https://issues.redhat.com/browse/JGRP-2466 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.2.2 > Reporter: Baoyi Chen > Assignee: Bela Ban > Priority: Minor > Attachments: alloc.svg > > > we use [async-profiler|https://github.com/jvm-profiling-tools/async-profiler] to profiling our project's temporary object allocation. found that jrgoups log.trace take up a certain amount of memory space. more details please refer the attachment. could we add isTraceEnabled() condition when print the trace log? that could be improve the temporary object allocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2466) add isTraceEnabled() when log.trace

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2466?page=com.atlassian.jira.plugin... ] Bela Ban closed JGRP-2466. -------------------------- Resolution: Rejected > add isTraceEnabled() when log.trace > ----------------------------------- > > Key: JGRP-2466 > URL: https://issues.redhat.com/browse/JGRP-2466 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.2.2 > Reporter: Baoyi Chen > Assignee: Bela Ban > Priority: Minor > Attachments: alloc.svg > > > we use [async-profiler|https://github.com/jvm-profiling-tools/async-profiler] to profiling our project's temporary object allocation. found that jrgoups log.trace take up a certain amount of memory space. more details please refer the attachment. could we add isTraceEnabled() condition when print the trace log? that could be improve the temporary object allocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5236) Decision table validation produces runtime exception in Business Central

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5236?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5236: ----------------------------------- Tester: Daniel Rosa Story Points: 1 > Decision table validation produces runtime exception in Business Central > ------------------------------------------------------------------------ > > Key: DROOLS-5236 > URL: https://issues.redhat.com/browse/DROOLS-5236 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Matteo Mortari > Priority: Minor > Attachments: Benefits Calculator.dmn > > > In Business Central's DMN Modeler, a decision table with "Unique" Hit policy and overlapping rules, when placed into a context, produces a Runtime Exception on validate. Error Message is: "[uuid] DMN: Validation of the DMN Model cannot be performed because of some runtime exception 'org.kie.dmn.model.v1_2.TContextEntry cannot be cast to org.kie.dmn.model.api.NamedElement'. (DMN Validation stopped on failed validation for some DMN Model)" > We expected to see 'DMN: Overlap detected: Overlap values: [...] for rules: [...]. UNIQUE hit policy decision tables can only have one matching rule' among the validation errors, and in fact this error is displayed when the decision table is not nested within a context. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5236) Decision table validation produces runtime exception in Business Central

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5236?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5236: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13) > Decision table validation produces runtime exception in Business Central > ------------------------------------------------------------------------ > > Key: DROOLS-5236 > URL: https://issues.redhat.com/browse/DROOLS-5236 > Project: Drools > Issue Type: Bug > Components: decision tables, DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Matteo Mortari > Priority: Minor > Attachments: Benefits Calculator.dmn > > > In Business Central's DMN Modeler, a decision table with "Unique" Hit policy and overlapping rules, when placed into a context, produces a Runtime Exception on validate. Error Message is: "[uuid] DMN: Validation of the DMN Model cannot be performed because of some runtime exception 'org.kie.dmn.model.v1_2.TContextEntry cannot be cast to org.kie.dmn.model.api.NamedElement'. (DMN Validation stopped on failed validation for some DMN Model)" > We expected to see 'DMN: Overlap detected: Overlap values: [...] for rules: [...]. UNIQUE hit policy decision tables can only have one matching rule' among the validation errors, and in fact this error is displayed when the decision table is not nested within a context. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5236) Decision table validation produces runtime exception in Business Central

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5236?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5236: ----------------------------------- Component/s: dmn engine (was: decision tables) (was: DMN Editor) > Decision table validation produces runtime exception in Business Central > ------------------------------------------------------------------------ > > Key: DROOLS-5236 > URL: https://issues.redhat.com/browse/DROOLS-5236 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Matteo Mortari > Priority: Minor > Attachments: Benefits Calculator.dmn > > > In Business Central's DMN Modeler, a decision table with "Unique" Hit policy and overlapping rules, when placed into a context, produces a Runtime Exception on validate. Error Message is: "[uuid] DMN: Validation of the DMN Model cannot be performed because of some runtime exception 'org.kie.dmn.model.v1_2.TContextEntry cannot be cast to org.kie.dmn.model.api.NamedElement'. (DMN Validation stopped on failed validation for some DMN Model)" > We expected to see 'DMN: Overlap detected: Overlap values: [...] for rules: [...]. UNIQUE hit policy decision tables can only have one matching rule' among the validation errors, and in fact this error is displayed when the decision table is not nested within a context. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5236) Decision table validation produces runtime exception in Business Central

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5236?page=com.atlassian.jira.plug... ] Matteo Mortari resolved DROOLS-5236. ------------------------------------ Resolution: Duplicate Issue > Decision table validation produces runtime exception in Business Central > ------------------------------------------------------------------------ > > Key: DROOLS-5236 > URL: https://issues.redhat.com/browse/DROOLS-5236 > Project: Drools > Issue Type: Bug > Components: decision tables, DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Matteo Mortari > Priority: Minor > Attachments: Benefits Calculator.dmn > > > In Business Central's DMN Modeler, a decision table with "Unique" Hit policy and overlapping rules, when placed into a context, produces a Runtime Exception on validate. Error Message is: "[uuid] DMN: Validation of the DMN Model cannot be performed because of some runtime exception 'org.kie.dmn.model.v1_2.TContextEntry cannot be cast to org.kie.dmn.model.api.NamedElement'. (DMN Validation stopped on failed validation for some DMN Model)" > We expected to see 'DMN: Overlap detected: Overlap values: [...] for rules: [...]. UNIQUE hit policy decision tables can only have one matching rule' among the validation errors, and in fact this error is displayed when the decision table is not nested within a context. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5236) Decision table validation produces runtime exception in Business Central

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5236?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5236: ---------------------------------------- [~tracyhires] this problem was already solved by [RHDM-1281] so bumping Drools version to 7.35.0.Final or higher should do it. My suggestion is to always try against the latest version, as there are chances the problem was already fixes ;) That said, thank you for sharing the model, as I believe one of the overlap messages, can be improved; I will work on it on a separa jira. To conclude, as this was solved by [RHDM-1281] going to mark it as Resolved, update Drools version. If there are still problems, don't hesitate to reopen this jira or file a new one. > Decision table validation produces runtime exception in Business Central > ------------------------------------------------------------------------ > > Key: DROOLS-5236 > URL: https://issues.redhat.com/browse/DROOLS-5236 > Project: Drools > Issue Type: Bug > Components: decision tables, DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Matteo Mortari > Priority: Minor > Attachments: Benefits Calculator.dmn > > > In Business Central's DMN Modeler, a decision table with "Unique" Hit policy and overlapping rules, when placed into a context, produces a Runtime Exception on validate. Error Message is: "[uuid] DMN: Validation of the DMN Model cannot be performed because of some runtime exception 'org.kie.dmn.model.v1_2.TContextEntry cannot be cast to org.kie.dmn.model.api.NamedElement'. (DMN Validation stopped on failed validation for some DMN Model)" > We expected to see 'DMN: Overlap detected: Overlap values: [...] for rules: [...]. UNIQUE hit policy decision tables can only have one matching rule' among the validation errors, and in fact this error is displayed when the decision table is not nested within a context. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5254) [DMN Designer] Generate SVG for use in Swagger documentation

by Michael Anstis (Jira)

Michael Anstis created DROOLS-5254: -------------------------------------- Summary: [DMN Designer] Generate SVG for use in Swagger documentation Key: DROOLS-5254 URL: https://issues.redhat.com/browse/DROOLS-5254 Project: Drools Issue Type: Feature Request Components: DMN Editor Affects Versions: 7.36.0.Final Reporter: Matteo Mortari Assignee: Guilherme Gomes {quote} It'd be nice to have the ability to generate SVGs for a DMN XML model (including graph and boxed expressions) using a utility class/function that does not require the editor to be deployed or running. The resulting SVG would be used in the Swagger documentation. {quote} Apparently the _process_ people have been looking into something similar for processes; so it might be worth checking with [~roger600] first as whatever DMN does may simply follow on from BPMN2/CM. There is possibly an existing DMN JIRA for a similar requirement (as, IIRC, "Export as SVG" only generates SVG for the graph at present and not the boxed expressions). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2466) add isTraceEnabled() when log.trace

by Baoyi Chen (Jira)

[ https://issues.redhat.com/browse/JGRP-2466?page=com.atlassian.jira.plugin... ] Baoyi Chen commented on JGRP-2466: ---------------------------------- additional class:method UNICAST3:createReceiverEntry UNICAST3:getReceiverEntry > add isTraceEnabled() when log.trace > ----------------------------------- > > Key: JGRP-2466 > URL: https://issues.redhat.com/browse/JGRP-2466 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.2.2 > Reporter: Baoyi Chen > Assignee: Bela Ban > Priority: Minor > Attachments: alloc.svg > > > we use [async-profiler|https://github.com/jvm-profiling-tools/async-profiler] to profiling our project's temporary object allocation. found that jrgoups log.trace take up a certain amount of memory space. more details please refer the attachment. could we add isTraceEnabled() condition when print the trace log? that could be improve the temporary object allocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 April 2020