February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4994: ------------------------------------ [~uxdlc] Thank you, both solutions are fine for me. In case of a short description, I prefer the first one. > Highlight better that expression and graphical collection editor are different > ------------------------------------------------------------------------------ > > Key: DROOLS-4994 > URL: https://issues.redhat.com/browse/DROOLS-4994 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Anna Dupliak > Assignee: Elizabeth Clayton > Priority: Minor > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png > > > Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698 > We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. > Suggested solution: > - to explain the difference directly in the popup, somewhere close to radio buttons create/define. > Example: > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! > How that works now: > Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" > What expression should be to make test pass: > (2 in ?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13053) Upgrade netty to 4.1.45.Final

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13053: --------------------------------- Summary: Upgrade netty to 4.1.45.Final Key: WFLY-13053 URL: https://issues.redhat.com/browse/WFLY-13053 Project: WildFly Issue Type: Component Upgrade Components: Clustering, JMS Affects Versions: 19.0.0.Beta1 Reporter: Ingo Weiss Assignee: Emmanuel Hugonnet -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13052) Workaround for MicroProfile Config TCK "ShouldThrowException" failure

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13052?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-13052: ------------------------------- Summary: Workaround for MicroProfile Config TCK "ShouldThrowException" failure (was: Workaround MicroProfile Config TCK "ShouldThrowException" failure) > Workaround for MicroProfile Config TCK "ShouldThrowException" failure > --------------------------------------------------------------------- > > Key: WFLY-13052 > URL: https://issues.redhat.com/browse/WFLY-13052 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Config > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > Some MicroProfile Config TCK tests expects deployment failure by annotating the @Deployment with @ShouldThrowException(DeploymentException.class). > Due to https://issues.redhat.com/browse/WFARQ-59, the deployment exception is not properly handled on the Arquillian client side and the test fails because, the thrown exception is not of the proper type. > This can be worked around by adding a DeploymentExceptionTransformer that will transform the exception into the proper type. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13052) Workaround for MicroProfile Config TCK "ShouldThrowException" failure

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13052?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-13052: ------------------------------- Issue Type: Bug (was: Component Upgrade) > Workaround for MicroProfile Config TCK "ShouldThrowException" failure > --------------------------------------------------------------------- > > Key: WFLY-13052 > URL: https://issues.redhat.com/browse/WFLY-13052 > Project: WildFly > Issue Type: Bug > Components: MP Config > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > Some MicroProfile Config TCK tests expects deployment failure by annotating the @Deployment with @ShouldThrowException(DeploymentException.class). > Due to https://issues.redhat.com/browse/WFARQ-59, the deployment exception is not properly handled on the Arquillian client side and the test fails because, the thrown exception is not of the proper type. > This can be worked around by adding a DeploymentExceptionTransformer that will transform the exception into the proper type. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13052) Workaround MicroProfile Config TCK "ShouldThrowException" failure

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-13052: ---------------------------------- Summary: Workaround MicroProfile Config TCK "ShouldThrowException" failure Key: WFLY-13052 URL: https://issues.redhat.com/browse/WFLY-13052 Project: WildFly Issue Type: Component Upgrade Components: MP Config Reporter: Jeff Mesnil Assignee: Jeff Mesnil Some MicroProfile Config TCK tests expects deployment failure by annotating the @Deployment with @ShouldThrowException(DeploymentException.class). Due to https://issues.redhat.com/browse/WFARQ-59, the deployment exception is not properly handled on the Arquillian client side and the test fails because, the thrown exception is not of the proper type. This can be worked around by adding a DeploymentExceptionTransformer that will transform the exception into the proper type. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1058) Document IPI vs UPI and how to find older cluster

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1058?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1058. ---------------------------------- Resolution: Done https://docs.jboss.org/display/SWSQE/FAQ > Document IPI vs UPI and how to find older cluster > ------------------------------------------------- > > Key: SWSQE-1058 > URL: https://issues.redhat.com/browse/SWSQE-1058 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9188) A StackOverflowError occurs when the server executes the "XA END" statement and the Oracle server exits abruptly

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/WFLY-9188?page=com.atlassian.jira.plugin... ] Mayank Kunwar reassigned WFLY-9188: ----------------------------------- Assignee: Mayank Kunwar > A StackOverflowError occurs when the server executes the "XA END" statement and the Oracle server exits abruptly > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9188 > URL: https://issues.redhat.com/browse/WFLY-9188 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.1.0.Final > Reporter: Jarek Przygódzki > Assignee: Mayank Kunwar > Priority: Major > Attachments: stacktrace.txt > > > A StackOverflowError occurs in the WildFly application server when the server executes the "XA END" statement and the Oracle server exits abruptly > JVM: OpenJDK Runtime Environment (build 1.8.0_121-b13) > OS: Red Hat Enterprise Linux Server release 7.3 (Maipo) > JDBC Driver version: 11.2.0.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5002) [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5002?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5002: -------------------------------- Steps to Reproduce: # Create structure like ## !Screenshot from 2020-02-04 07-50-43.png|thumbnail! # Click plus next to *tIllness* ## !Screenshot from 2020-02-04 07-50-53.png|thumbnail! Current: *Medicine* field is expanded Expected: *Medicine* field remains collapsed > [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field > ---------------------------------------------------------------------------------- > > Key: DROOLS-5002 > URL: https://issues.redhat.com/browse/DROOLS-5002 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-02-04 07-50-43.png, Screenshot from 2020-02-04 07-50-53.png > > > Issue found during DROOLS-4485 review. > When user insert a sibling field in a structure, that contains one field of a structure type, this structure field is expanded, even if it was collapsed before. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5002) [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5002?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5002: -------------------------------- Description: Issue found during DROOLS-4485 review. When user insert a sibling field in a structure, that contains one field of a structure type, this structure field is expanded, even if it was collapsed before. was: Show a visual indication of the current drag level. See (the blue line): !image-2019-08-27-12-40-51-854.png|width=500! > [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field > ---------------------------------------------------------------------------------- > > Key: DROOLS-5002 > URL: https://issues.redhat.com/browse/DROOLS-5002 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-02-04 07-50-43.png, Screenshot from 2020-02-04 07-50-53.png > > > Issue found during DROOLS-4485 review. > When user insert a sibling field in a structure, that contains one field of a structure type, this structure field is expanded, even if it was collapsed before. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5002) [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5002?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5002: -------------------------------- Attachment: Screenshot from 2020-02-04 07-50-53.png Screenshot from 2020-02-04 07-50-43.png > [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field > ---------------------------------------------------------------------------------- > > Key: DROOLS-5002 > URL: https://issues.redhat.com/browse/DROOLS-5002 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-02-04 07-50-43.png, Screenshot from 2020-02-04 07-50-53.png > > > Issue found during DROOLS-4485 review. > When user insert a sibling field in a structure, that contains one field of a structure type, this structure field is expanded, even if it was collapsed before. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 February 2020