January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12935) Replace Java EE7 Concurrency RI with Jakarta EE 8 Concurrency RI

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12935: -------------------------------------- Summary: Replace Java EE7 Concurrency RI with Jakarta EE 8 Concurrency RI Key: WFLY-12935 URL: https://issues.redhat.com/browse/WFLY-12935 Project: WildFly Issue Type: Enhancement Components: Concurrency Utilities Reporter: Eduardo Martins Assignee: Eduardo Martins The new Jakarta EE8 Concurrency RI is fully compatible with Java EE7 Concurrency RI and besides already including a few bug fixes its development is active, thus it makes sense to upgrade the base framework of WildFly EE Concurrency Utilities implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2841) [DMN Designer] Sort item definitions of the model

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-2841?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-2841: -------------------------------- Priority: Minor (was: Major) > [DMN Designer] Sort item definitions of the model > ------------------------------------------------- > > Key: DROOLS-2841 > URL: https://issues.redhat.com/browse/DROOLS-2841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > The DMN model file can contain custom item definitions. These are then shown in the data type picker dialog. Currently these definitions are not sorted in the dialog. We should sort them and their attributes alphabetically (a -> z). > Possibility to change key for sorting shouldn't be implemented. If such requirement appears in future, will be implemented in separate jira. > h2. Acceptance Test > - Ordering of {{A a B b C c}} doesn't result to {{A B C a b c}} > - Ordering is applied in properties panel, output data type selectbox > - Ordering is applied in *Manage custom data type* dialog > - Changes in *Manage custom data type* dialog are reflected into > -- *Manage custom data type* dialog > -- output data type selectbox -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4869) [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4869?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4869: -------------------------------- Affects Version/s: 7.32.0.Final > [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table > ------------------------------------------------------------------------------------ > > Key: DROOLS-4869 > URL: https://issues.redhat.com/browse/DROOLS-4869 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: steps-to-reproduce.mp4 > > > When users click on a list of that types that has a scroll bar, the screen unexpectedly jumps to a non-related data type. > See the steps to reproduce: > [^steps-to-reproduce.mp4] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4869) [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4869?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4869: -------------------------------- Issue Type: Bug (was: Task) > [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table > ------------------------------------------------------------------------------------ > > Key: DROOLS-4869 > URL: https://issues.redhat.com/browse/DROOLS-4869 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: steps-to-reproduce.mp4 > > > When users click on a list of that types that has a scroll bar, the screen unexpectedly jumps to a non-related data type. > See the steps to reproduce: > [^steps-to-reproduce.mp4] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-293) Current implementation of MP-JWT doesn't require claims which should be required

by Jan Kasik (Jira)

Jan Kasik created WFWIP-293: ------------------------------- Summary: Current implementation of MP-JWT doesn't require claims which should be required Key: WFWIP-293 URL: https://issues.redhat.com/browse/WFWIP-293 Project: WildFly WIP Issue Type: Bug Components: MP JWT Reporter: Jan Kasik Assignee: Darran Lofthouse Chapter 4.1 of MP-JWT 1.1 recommends minimal set of JWT claims which should be required. Current implementation doesn't check for following claims and returns 200/OK if they are missing: * {{upn}} * {{jti}} * {{groups}} * {{iat}} * {{sub}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12934) Remove link to google plus on https://wildfly.org/

by Jpa Ge (Jira)

Jpa Ge created WFLY-12934: ----------------------------- Summary: Remove link to google plus on https://wildfly.org/ Key: WFLY-12934 URL: https://issues.redhat.com/browse/WFLY-12934 Project: WildFly Issue Type: Bug Reporter: Jpa Ge Assignee: Brian Stansberry On the website, https://wildfly.org/, in the "Follow us" menu, there an sub menu for google plus. But google plus was turned off in december 2018. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4904) DMN raise RTF wrong PMT example

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4904?page=com.atlassian.jira.plug... ] Matteo Mortari resolved DROOLS-4904. ------------------------------------ Resolution: Done done with https://issues.omg.org/browse/INBOX-939 > DMN raise RTF wrong PMT example > ------------------------------- > > Key: DROOLS-4904 > URL: https://issues.redhat.com/browse/DROOLS-4904 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > report wrong example as described in [DROOLS-4812] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4904) DMN raise RTF wrong PMT example

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4904: -------------------------------------- Summary: DMN raise RTF wrong PMT example Key: DROOLS-4904 URL: https://issues.redhat.com/browse/DROOLS-4904 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari report wrong example as described in [DROOLS-4812] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11388) User is not informed about incorrect values in exposed-subsystems for MP Metrics

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-11388?page=com.atlassian.jira.plugi... ] Lin Gao commented on WFLY-11388: -------------------------------- Update PR: https://github.com/wildfly/wildfly/pull/12884 > User is not informed about incorrect values in exposed-subsystems for MP Metrics > -------------------------------------------------------------------------------- > > Key: WFLY-11388 > URL: https://issues.redhat.com/browse/WFLY-11388 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Lin Gao > Priority: Major > > User is not informed about incorrect values in exposed-subsystems for MP Metrics > When I do stuff like > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"]) > {code} > instead of > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch-jberet"]) > {code} > I get no warning about non-existing subsystem. > User should be informed about misconfiguration. > Question is when: > - when server boots > - when the cli / management command is invoked > - both cases -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11388) User is not informed about incorrect values in exposed-subsystems for MP Metrics

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-11388?page=com.atlassian.jira.plugi... ] Lin Gao updated WFLY-11388: --------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12884 (was: https://github.com/wildfly/wildfly/pull/11998) > User is not informed about incorrect values in exposed-subsystems for MP Metrics > -------------------------------------------------------------------------------- > > Key: WFLY-11388 > URL: https://issues.redhat.com/browse/WFLY-11388 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Lin Gao > Priority: Major > > User is not informed about incorrect values in exposed-subsystems for MP Metrics > When I do stuff like > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"]) > {code} > instead of > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch-jberet"]) > {code} > I get no warning about non-existing subsystem. > User should be informed about misconfiguration. > Question is when: > - when server boots > - when the cli / management command is invoked > - both cases -- 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 January 2020