December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3048) [DMN Designer] CellEditorControl needs to issue a new instance per use

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3048?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-3048: ----------------------------------- Description: A {{Popover}} used to edit a cell or column header (or any other DOM-based editor for that matter) disappears following a change in the widget that causes a {{Layer.draw()}} if the grid is sufficiently wide that there is a column not visible on screen. All cells/columns that use {{CellEditorControls}} (containing, for example, the {{Popover}}) share a single instance from {{CellEditorControl}} and hence although the User makes a change in a visible column the invisible column (scrolled off screen) has its DOM resources destroyed that is the same instance as that for the visible column. See https://github.com/kiegroup/appformer/blob/master/uberfire-extensions/ube.... If a column is not in the _body_ or _floating_ columns collection its DOM resources are destroyed. I probably need to ensure different instances of {{CellEditorControl}} are created for each column/cell where we currently share the same instance. Also check for destruction of DOM elements in {{Document}} when grids/columns etc are destroyed. h3. Acceptance criteria # Create a DMN model # Add a Decision # Set its expression to a Decision Table # Add multiple Input and Output columns so that the table is wider than the visible screen space (i.e. some columns are not rendered) # Click on the header of a visible column # The Name/Data-type popup should appear # Repeat for expression type of Relation was: A {{Popover}} used to edit a cell or column header (or any other DOM-based editor for that matter) disappears following a change in the widget that causes a {{Layer.draw()}} if the grid is sufficiently wide that there is a column not visible on screen. All cells/columns that use {{CellEditorControls}} (containing, for example, the {{Popover}}) share a single instance from {{CellEditorControl}} and hence although the User makes a change in a visible column the invisible column (scrolled off screen) has its DOM resources destroyed that is the same instance as that for the visible column. See https://github.com/kiegroup/appformer/blob/master/uberfire-extensions/ube.... If a column is not in the _body_ or _floating_ columns collection its DOM resources are destroyed. I probably need to ensure different instances of {{CellEditorControl}} are created for each column/cell where we currently share the same instance. Also check for destruction of DOM elements in {{Document}} when grids/columns etc are destroyed. > [DMN Designer] CellEditorControl needs to issue a new instance per use > ---------------------------------------------------------------------- > > Key: DROOLS-3048 > URL: https://issues.redhat.com/browse/DROOLS-3048 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > A {{Popover}} used to edit a cell or column header (or any other DOM-based editor for that matter) disappears following a change in the widget that causes a {{Layer.draw()}} if the grid is sufficiently wide that there is a column not visible on screen. > All cells/columns that use {{CellEditorControls}} (containing, for example, the {{Popover}}) share a single instance from {{CellEditorControl}} and hence although the User makes a change in a visible column the invisible column (scrolled off screen) has its DOM resources destroyed that is the same instance as that for the visible column. > See https://github.com/kiegroup/appformer/blob/master/uberfire-extensions/ube.... If a column is not in the _body_ or _floating_ columns collection its DOM resources are destroyed. > I probably need to ensure different instances of {{CellEditorControl}} are created for each column/cell where we currently share the same instance. Also check for destruction of DOM elements in {{Document}} when grids/columns etc are destroyed. > h3. Acceptance criteria > # Create a DMN model > # Add a Decision > # Set its expression to a Decision Table > # Add multiple Input and Output columns so that the table is wider than the visible screen space (i.e. some columns are not rendered) > # Click on the header of a visible column > # The Name/Data-type popup should appear > # Repeat for expression type of Relation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11787) Add test case for JBEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-11787?page=com.atlassian.jira.plugi... ] Darran Lofthouse reopened WFLY-11787: ------------------------------------- > Add test case for JBEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11787 > URL: https://issues.redhat.com/browse/WFLY-11787 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Daniel Cihak > Assignee: Daniel Cihak > Priority: Major > Labels: test > > Add a test case for BEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1008) Code coverage on OCP 4.2

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1008?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1008. ---------------------------------- Resolution: Done Easier option was to continue using UPI for OCP 4.2 instead of using IPI for OCP 4.2. There is no need to change the way how is the code coverage implemented. > Code coverage on OCP 4.2 > ------------------------ > > Key: SWSQE-1008 > URL: https://issues.redhat.com/browse/SWSQE-1008 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > How to get code coverage report from VMs created by ocp installer? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1044) Reinstall kiali auto1 and auto2 clusters to OCP 4.2 version

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1044?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1044. ---------------------------------- Resolution: Done Nightly automation is working fine on OCP 4.2 > Reinstall kiali auto1 and auto2 clusters to OCP 4.2 version > ----------------------------------------------------------- > > Key: SWSQE-1044 > URL: https://issues.redhat.com/browse/SWSQE-1044 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > OCP 4.1 will be not supported soon. We need to run automation on OCP 4.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12886) WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient

by Matěj Novotný (Jira)

[ https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugi... ] Matěj Novotný commented on WFLY-12886: -------------------------------------- Hmm, I cannot reproduce the problem. I took a [WFLY quickstart|https://github.com/wildfly/quickstart/tree/18.0.1.Final/paymen...] that uses CDI bean with discovery mode {{all}}, added your class in, added a method that somehow utilized {{HttpClient}} (else it was just an empty import), then called this method from a bean. And I still don't see {{WELD-000119}} in the log... > WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-12886 > URL: https://issues.redhat.com/browse/WFLY-12886 > Project: WildFly > Issue Type: Enhancement > Components: CDI / Weld > Affects Versions: 17.0.1.Final > Reporter: nimo stephan > Assignee: Matěj Novotný > Priority: Minor > > I get this info when starting wildfly server: > {code:java} > 01:33:09,168 INFO [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. > {code} > My WebUtils.class imports: > {code:java} > import java.net.URI; > import java.net.http.HttpClient; > import java.net.http.HttpRequest; > import java.net.http.HttpResponse.BodyHandlers; > {code} > Should I include java se module by myself in wildfly to remove this log? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-289) Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFWIP-289?page=com.atlassian.jira.plugin... ] Fabio Burzigotti updated WFWIP-289: ----------------------------------- Steps to Reproduce: The issue can be reproduced following the steps: * clone the EAP MicroProfile TS fork [1] and executing the following command: $ mvn clean verify -pl microprofile-open-api -Djboss.home=<FEATURE_BRANCH_DIST_JBOSS_HOME> -Pmp-open-api -Dtest=MicroprofileConfigIntegrationTests -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent -Djava.compiler=NONE" * remove the @Ignore clause from last 3 tests in MicroprofileConfigIntegrationTests.java * place a breakpoint at one of the tests first line * when the breakpoint is hit, inspect generated OpenAPI doc at `http://localhost:8080/openapi` * check test results, 2 or 3 related tests should be failing Used feature branch is: https://github.com/pferraro/wildfly/tree/WFLY-12313 [1] https://github.com/fabiobrz/eap-microprofile-test-suite/tree/integration-... was: The issue can be reproduced following the steps: * clone the EAP MicroProfile TS fork [1] and executing the following command: $ mvn clean verify -pl microprofile-open-api -Djboss.home=<FEATURE_BRANCH_DIST_JBOSS_HOME> -Pmp-open-api -Dtest=MicroprofileConfigIntegrationTests -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent -Djava.compiler=NONE" * remove the @Ignore clause from last 3 tests * place a breakpoint at one of the tests first line * when the breakpoint is hit, inspect generated OpenAPI doc at `http://localhost:8080/openapi` * check test results, 3 related tests should be failing Used feature branch is: https://github.com/pferraro/wildfly/tree/WFLY-12313 [1] https://github.com/fabiobrz/eap-microprofile-test-suite/tree/integration-... > Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues > -------------------------------------------------------------------------------------------- > > Key: WFWIP-289 > URL: https://issues.redhat.com/browse/WFWIP-289 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Blocker > > Complex scenario with 4 subsequent deployments. > The last one adds the `mp.openapi.scan.disable=true` MP Config core property - consequently no `mp.openapi.extensions.path` MP Config vendor extension property is defined. > This causes the server to behave in non-deterministic way for generation of OpenAPI document at standard `/openapi` URL. > "Non-deterministic" means that - when the test is executed several times - the generated document contains elements either from first or second deployments (third one is not registering the endpoint and is skipped as expected). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-289) Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues

by Fabio Burzigotti (Jira)

Fabio Burzigotti created WFWIP-289: -------------------------------------- Summary: Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues Key: WFWIP-289 URL: https://issues.redhat.com/browse/WFWIP-289 Project: WildFly WIP Issue Type: Bug Components: MP OpenAPI Reporter: Fabio Burzigotti Assignee: Paul Ferraro Complex scenario with 4 subsequent deployments. The last one adds the `mp.openapi.scan.disable=true` MP Config core property - consequently no `mp.openapi.extensions.path` MP Config vendor extension property is defined. This causes the server to behave in non-deterministic way for generation of OpenAPI document at standard `/openapi` URL. "Non-deterministic" means that - when the test is executed several times - the generated document contains elements either from first or second deployments (third one is not registering the endpoint and is skipped as expected). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12903) EJBComponent may throw NPE in certain conditions from checkCallerSecurityIdentityRole

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-12903?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFLY-12903: ----------------------------------------- Probably also should add something to the Elytron methods to ensure a null roles can not be returned from the SecurityIdentity > EJBComponent may throw NPE in certain conditions from checkCallerSecurityIdentityRole > ------------------------------------------------------------------------------------- > > Key: WFLY-12903 > URL: https://issues.redhat.com/browse/WFLY-12903 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > > If there is custom role mapping set up in elytron and it does not handle it properly 'roles' might end up null: https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12903) EJBComponent may throw NPE in certain conditions from checkCallerSecurityIdentityRole

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-12903?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-12903: ------------------------------------ Issue Type: Bug (was: Enhancement) > EJBComponent may throw NPE in certain conditions from checkCallerSecurityIdentityRole > ------------------------------------------------------------------------------------- > > Key: WFLY-12903 > URL: https://issues.redhat.com/browse/WFLY-12903 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > > If there is custom role mapping set up in elytron and it does not handle it properly 'roles' might end up null: https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12903) EJBComponent may throw NPE in certain conditions from checkCallerSecurityIdentityRole

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-12903?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-12903: ------------------------------------ Priority: Major (was: Minor) > EJBComponent may throw NPE in certain conditions from checkCallerSecurityIdentityRole > ------------------------------------------------------------------------------------- > > Key: WFLY-12903 > URL: https://issues.redhat.com/browse/WFLY-12903 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > > If there is custom role mapping set up in elytron and it does not handle it properly 'roles' might end up null: https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019