October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4625: ------------------------------------------- [~danielezonca] So the user should go to the alerts or the background tab to get more info? Or both? > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-10-16 16-42-25.png, Screenshot from 2019-10-16 16-44-18.png, background-error.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4625: --------------------------------------- [~uxdlc] !Screenshot from 2019-10-16 16-42-25.png|thumbnail! Run failed because of wrong values in scenarios !Screenshot from 2019-10-16 16-44-18.png|thumbnail! Run failed because of compilation errors (and after clicking on "View Alerts"). This should not happen often. As you can see in the second screenshot the only "information" we might be able to add with the current implementation is a different message in the alert panel (to warn user about wrong background data) but nothing more. Considering I expect wrong data in background could be something that happen many times I think it should be nice to add some other indicator/information for the user to cover this use case. > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-10-16 16-42-25.png, Screenshot from 2019-10-16 16-44-18.png, background-error.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12678) Upgrade org.jboss.spec.javax.ws.jboss-jaxrs-api_2.1_spec to 2.0.1.Final

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-12678: -------------------------------------- Summary: Upgrade org.jboss.spec.javax.ws.jboss-jaxrs-api_2.1_spec to 2.0.1.Final Key: WFLY-12678 URL: https://issues.jboss.org/browse/WFLY-12678 Project: WildFly Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Alessio Soldano -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12678) Upgrade org.jboss.spec.javax.ws.jboss-jaxrs-api_2.1_spec to 2.0.1.Final

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12678?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-12678: ----------------------------------- Fix Version/s: 19.0.0.Beta1 > Upgrade org.jboss.spec.javax.ws.jboss-jaxrs-api_2.1_spec to 2.0.1.Final > ----------------------------------------------------------------------- > > Key: WFLY-12678 > URL: https://issues.jboss.org/browse/WFLY-12678 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 19.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4653) Documents Container builds on Openshift 4.x

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4653: ------------------------------------------ Summary: Documents Container builds on Openshift 4.x Key: DROOLS-4653 URL: https://issues.jboss.org/browse/DROOLS-4653 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12676) org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12676?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12676: ------------------------------------- This memory leak also occurs with the current WildFly master (built with 4854248f9df123fec1a188bba8209e150006d74c as latest commit). Also creates with WildFly 18.0.0.Final. > org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment > ------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12676 > URL: https://issues.jboss.org/browse/WFLY-12676 > Project: WildFly > Issue Type: Task > Components: JCA > Affects Versions: 18.0.0.Final > Reporter: Scott Marlow > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 19.0.0.Beta1 > > Attachments: 2lc.jar, java_pid12802.0001.zip, jcaleakmarlow.txt > > > As part of looking at [WFLY-12671], I found that org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is leaking the application classloader (after undeployment) via org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory originalTCCL being kept after undeployment. > See attached jcaleakmarlow.txt (also attached to [WFLY-12671]), which shows the leak. > I tried waiting a few minutes after undeployment and the leak was still there. I also tried an even simpler app (2lc.jar) and still there is a leak. I also attached the heapdump (java_pid12802.0001.zip) > To recreate: > * Deploy simple (no app code will be executed) 2lc.jar app. > * Undeploy by doing "rm 2lc.jar.deployed" in wildfly/standalone/deployments > * Look at memory with MAT or other memory leak tool. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4652) Remove Thorntail module from HACEP

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4652: ------------------------------------------ Summary: Remove Thorntail module from HACEP Key: DROOLS-4652 URL: https://issues.jboss.org/browse/DROOLS-4652 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4625: ---------------------------------- Attachment: Screenshot from 2019-10-16 16-42-25.png > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-10-16 16-42-25.png, Screenshot from 2019-10-16 16-44-18.png, background-error.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4625: ---------------------------------- Attachment: Screenshot from 2019-10-16 16-44-18.png > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-10-16 16-42-25.png, Screenshot from 2019-10-16 16-44-18.png, background-error.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4651) Scenario: Review Save interaction in Settings panel.

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4651: ---------------------------------------- [~uxdlc] No we don't have that in DMN :-) > Scenario: Review Save interaction in Settings panel. > ----------------------------------------------------- > > Key: DROOLS-4651 > URL: https://issues.jboss.org/browse/DROOLS-4651 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: 2019-10-15-1.png, 2019-10-15.png > > > The use of a Save button in the Settings panel is inconsistent with other "properties" panel in the overall application. The purpose of this jira is to revisit the use case scenarios to determine if the inclusion of the Save button here is appropriate. > Verification conditions: > * Documented rationale for the keeping the Save button, as is, with Team acceptance. > or > * Documented rationale for removing the Save button, with Team acceptance, in addition to any design changes needed as a result of its removal. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 October 2019