April 2020 - jboss-jira - Jboss List Archives

[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: -------------------------------- Where exactly (class:method) do you see this? The attached SVG doesn't show this in any JGroups class! > 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2468) Remove osgi and replace version in XML sample configs correctly

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2468?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2468. ---------------------------- Resolution: Done > Remove osgi and replace version in XML sample configs correctly > --------------------------------------------------------------- > > Key: JGRP-2468 > URL: https://issues.redhat.com/browse/JGRP-2468 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}. See JGRP-2467 for details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5203: --------------------------------- Story Points: 3 (was: 5) > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5210) BRL Column support for GDST to XLS export

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5210?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5210: --------------------------------- Story Points: 0 (was: 5) > BRL Column support for GDST to XLS export > ----------------------------------------- > > Key: DROOLS-5210 > URL: https://issues.redhat.com/browse/DROOLS-5210 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > How good the support will end up being is still open. The goal is to have one column for each variable, but if this is doable or not will depend on the limitations of the XLS table. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5046) [DMN Designer] Marshalling questions

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5046?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5046: --------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13)) > [DMN Designer] Marshalling questions > ------------------------------------ > > Key: DROOLS-5046 > URL: https://issues.redhat.com/browse/DROOLS-5046 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Michael Anstis > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Our marshaller is EXPLICITLY setting Definitions.typeLanguage to FEEL. Is this acceptable? > DMN1.2 Specification "6.3.2 Definitions metamodel" states : > An instance of Definitions MAY specify a typeLanguage, which is a URI that identifies the default type language used in elements within the scope of this Definitions ... If unspecified, the default typeLanguage is FEEL. > So it is not wrong, but it is not necessary. > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting ItemDefinition.id > DMN1.2 Specification "7.3.2 - ItemDefinition metamodel" states : > ...an instance of ItemDefinition HAS a name and an OPTIONAL id > So it is not wrong, but it is not necessary. > --------------------------------------------------------------------------------- > Our marshaller IS NOT setting ContextEntry.id > DMN1.2 Specification 10.5.2 - ContextEntry metamodel states : > ...ContextEntry is a specialization of DMNElement, from which it INHERITS the OPTIONAL id... > It is therefore correct for us to exclude the id (but _other tools_ includes it. Is that wrong?!) > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting DecisionTable.preferredOrientation (to Rule-as-Row) > DMN1.2 Specification 8.3.1 - Decision Table metamodel states : > ...It has a preferredOrientation, which SHALL be one of the enumerated DecisionTableOrientation. > It is therefore not wrong for us to include preferredOrientation and seems mandatory. > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting inputExpression.id. > DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel:- > ...An instance of InputClause is made of an optional inputExpression... [where an inputExpression is an Expression]. > There is not mention as to whether the Expression inherits its id or needs one explicitly defined. > Is it therefore incorrect for us to include the id? > --------------------------------------------------------------------------------- > Our marshaller IS NOT setting outputEntry.expressionLanguage. > DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel states (well does NOT state anything!) : > OutputClause does not appear to have an expressionLanguage property; only the UnaryTests that is encapsulated by OutputClause supports it. > Is this an issue with _other tools_'s marshaller? > --------------------------------------------------------------------------------- > [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation > https://issues.redhat.com/browse/DROOLS-5045 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2467: -------------------------------- Hi [~reinhapa] Running the testsuite now. If everything's peachy, I'll release a 4.2.3 within the next few minutes. Cheers, > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2467. ---------------------------- Resolution: Duplicate Issue Created new issue JGRP-2468 > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2467: --------------------------- Fix Version/s: 4.2.3 > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2468) Remove osgi and replace version in XML sample configs correctly

by Bela Ban (Jira)

Bela Ban created JGRP-2468: ------------------------------ Summary: Remove osgi and replace version in XML sample configs correctly Key: JGRP-2468 URL: https://issues.redhat.com/browse/JGRP-2468 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.2.3 The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2468) Remove osgi and replace version in XML sample configs correctly

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2468?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2468: --------------------------- Description: The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}. See JGRP-2467 for details. (was: The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}.) > Remove osgi and replace version in XML sample configs correctly > --------------------------------------------------------------- > > Key: JGRP-2468 > URL: https://issues.redhat.com/browse/JGRP-2468 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}. See JGRP-2467 for details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 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 April 2020