July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5029) Loose of focus after cloasing Collection Editor

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5029?page=com.atlassian.jira.plug... ] Yeser Amer resolved DROOLS-5029. -------------------------------- Fix Version/s: 7.41.0.Final Resolution: Duplicate Issue Duplicate of https://issues.redhat.com/browse/DROOLS-5511 > Loose of focus after cloasing Collection Editor > ----------------------------------------------- > > Key: DROOLS-5029 > URL: https://issues.redhat.com/browse/DROOLS-5029 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.33.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Optional > Labels: drools-tools > Fix For: 7.41.0.Final > > > When user finishes with editing collections, using Collection Editor and push *Close* or *Save* or *Cansel* then Grid of Test scenario is loosing focus and user unable to navigate it by keyboard. > Suggested behaviour: > When Collection Editor disappears after editing Collection cell A then focus should be on the cell of A. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13680) Generated metrics have duplicate labels

by Ivona Skorjanc (Jira)

Ivona Skorjanc created WFLY-13680: ------------------------------------- Summary: Generated metrics have duplicate labels Key: WFLY-13680 URL: https://issues.redhat.com/browse/WFLY-13680 Project: WildFly Issue Type: Bug Components: CLI Reporter: Ivona Skorjanc Assignee: Jean Francois Denise Attachments: kc_metric.txt We are using Keycloak which generates metrics using the jBoss CLI: [https://github.com/keycloak/keycloak-containers/blob/master/server/tools/...] We want to use Telegraf (with the Prometheus input plugin) to read the generated metrics. However, we get the following error: {{Error in plugin: error reading metrics for [http://localhost:9990/metrics]: reading text format failed: text format parsing error in line 34: second HELP line for metric name "base_gc_total"}} The base_gc_total metric appears twice for some reason. See the full metrics output in the attachment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5515) Document Ends with Chapter 5.8, should have more

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5515?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5515. --------------------------------- Resolution: Out of Date You'r pointing out to docs that is at least 10 years old. Please refer to https://docs.jboss.org/drools/release/7.39.0.Final/drools-docs/html_single/ > Document Ends with Chapter 5.8, should have more > ------------------------------------------------ > > Key: DROOLS-5515 > URL: https://issues.redhat.com/browse/DROOLS-5515 > Project: Drools > Issue Type: Bug > Reporter: Charles Herrick > Assignee: Mario Fusco > Priority: Minor > > [htt|https://docs.drools.org/5.2.0.Final/drools-expert-docs/html_single/??...] [ps://docs.drools.org/5.2.0.Final/drools-expert-docs/html_single/???#d0e61...] > > document ends with Chapter 5.8 but should have lots more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5515) Document Ends with Chapter 5.8, should have more

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5515?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5515: -------------------------------- Sprint: 2020 Week 28-30 (from Jul 6) > Document Ends with Chapter 5.8, should have more > ------------------------------------------------ > > Key: DROOLS-5515 > URL: https://issues.redhat.com/browse/DROOLS-5515 > Project: Drools > Issue Type: Bug > Reporter: Charles Herrick > Assignee: Mario Fusco > Priority: Minor > > [htt|https://docs.drools.org/5.2.0.Final/drools-expert-docs/html_single/??...] [ps://docs.drools.org/5.2.0.Final/drools-expert-docs/html_single/???#d0e61...] > > document ends with Chapter 5.8 but should have lots more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5518) DMN strongly typed class compile errors for capitalized/non-capitalized properties conflict

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5518?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5518: -------------------------------------- Description: If we have node names where the difference is only "First letter is capitalized or not" (e.g. "myPerson" and "MyPerson"), it will cause a compile error for InputSet and OutputSet. Note that it works fine without typesafe. - DMNRuntimeTypesTest.testCapitalLetterConflict() - DMNRuntimeTypesTest.testCapitalLetterConflictWithInputAndDecision() https://github.com/kiegroup/drools/pull/2993#discussion_r456300584 was: If we have node names where the difference is only "First letter is capitalized or not" (e.g. "myPerson" and "MyPerson"), it will cause a compile error for InputSet and OutputSet. Note that it works fine without typesafe. https://github.com/kiegroup/drools/pull/2993#discussion_r456300584 Steps to Reproduce: (was: - DMNRuntimeTypesTest.testCapitalLetterConflict()) > DMN strongly typed class compile errors for capitalized/non-capitalized properties conflict > ------------------------------------------------------------------------------------------- > > Key: DROOLS-5518 > URL: https://issues.redhat.com/browse/DROOLS-5518 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > If we have node names where the difference is only "First letter is capitalized or not" (e.g. "myPerson" and "MyPerson"), it will cause a compile error for InputSet and OutputSet. Note that it works fine without typesafe. > - DMNRuntimeTypesTest.testCapitalLetterConflict() > - DMNRuntimeTypesTest.testCapitalLetterConflictWithInputAndDecision() > https://github.com/kiegroup/drools/pull/2993#discussion_r456300584 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5053) Prometheus JMX exporter jar, stops starting the wildfly server.

by Rakesh Kumar Shah (Jira)

[ https://issues.redhat.com/browse/WFCORE-5053?page=com.atlassian.jira.plug... ] Rakesh Kumar Shah commented on WFCORE-5053: ------------------------------------------- Thank you James. When is the release of wild fly 21? > Prometheus JMX exporter jar, stops starting the wildfly server. > ---------------------------------------------------------------- > > Key: WFCORE-5053 > URL: https://issues.redhat.com/browse/WFCORE-5053 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Rakesh Kumar Shah > Assignee: James Perkins > Priority: Major > Fix For: 13.0.0.Beta1 > > > Trying to integrate the Prometheus JMX exporter with wildfly. After spending lot of time and work around it, wildfly is not starting. It throws following exception. > {code} > java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239) > at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223) > at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648) > at java.logging/java.util.logging.Logger.getLogger(Logger.java:717) > at java.logging/java.util.logging.Logger.getLogger(Logger.java:701) > at io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.<clinit>(JmxCollector.java:39) > at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:29) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) > at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) > WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level > at java.base/java.lang.Class.forName0(Native Method) > at java.base/java.lang.Class.forName(Class.java:398) > at org.jboss.modules.Module.run(Module.java:340) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:617) > Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:183) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5517: -------------------------------------- Description: DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext().getXXX() directly. https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 was: DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext().getXXX() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5519) Improve OutputSet to have FEELFunction fields rather than Object

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5519: ----------------------------------------- Summary: Improve OutputSet to have FEELFunction fields rather than Object Key: DROOLS-5519 URL: https://issues.redhat.com/browse/DROOLS-5519 Project: Drools Issue Type: Enhancement Components: dmn engine Affects Versions: 7.40.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi Currently OutputSet have Object fields to store FEELFunction for DecisionService/BKM context values. This Jira is to enhance to have org.kie.dmn.feel.runtime.FEELFunction in the generated OutputSet. https://github.com/kiegroup/drools/pull/2993/files#r455626598 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5518) DMN strongly typed class compile errors for capitalized/non-capitalized properties conflict

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5518: ----------------------------------------- Summary: DMN strongly typed class compile errors for capitalized/non-capitalized properties conflict Key: DROOLS-5518 URL: https://issues.redhat.com/browse/DROOLS-5518 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.40.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi If we have node names where the difference is only "First letter is capitalized or not" (e.g. "myPerson" and "MyPerson"), it will cause a compile error for InputSet and OutputSet. Note that it works fine without typesafe. https://github.com/kiegroup/drools/pull/2993#discussion_r456300584 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi edited comment on DROOLS-5517 at 7/19/20 10:23 PM: --------------------------------------------------------------------- Ideas: - Add a method to get OutputSet from DMNContext impl (and want isTypeSafe() method in Interface?) - Option A) -- Share DMNContextFPAImpl for both InputSet and OutputSet -- DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance -- DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity - Option B) -- Map and Recreate DMNContext right before returning evaluateXXX(). [https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core...] was (Author: tkobayashi): Ideas: - Add a method to get OutputSet from DMNContext impl (and want isTypeSafe() method in Interface?) - Option A) -- Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency -- DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance -- DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity - Option B) -- Map and Recreate DMNContext right before returning evaluateXXX(). [https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core...] > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 July 2020