October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12677) Mojarra Issue 4547 - ELFlash ArrayIndexOutOfBoundsException on invalid Cookie value

by Farah Juma (Jira)

Farah Juma created WFLY-12677: --------------------------------- Summary: Mojarra Issue 4547 - ELFlash ArrayIndexOutOfBoundsException on invalid Cookie value Key: WFLY-12677 URL: https://issues.jboss.org/browse/WFLY-12677 Project: WildFly Issue Type: Bug Components: JSF Reporter: Farah Juma Assignee: Farah Juma Backport the fix for [Mojarra Issue #4547|https://github.com/eclipse-ee4j/mojarra/issues/4547] once it has been approved upstream. The upstream PR is here: https://github.com/eclipse-ee4j/mojarra/pull/4548 -- 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 Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4651: -------------------------------------- Attachment: 2019-10-15-1.png > 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

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

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4651: -------------------------------------- Attachment: 2019-10-15.png > 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

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

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4651: ------------------------------------------- [~porcelli] [~gabriolo] So if I'm following, the inconsistency then is with the segregation of save actions - settings as distinct from grid data saving? [~manstis] we don't have this distinction in DMN do we? > 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 > > 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

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

by Scott Marlow (Jira)

Scott Marlow created WFLY-12676: ----------------------------------- Summary: 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 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-4651) Scenario: Review Save interaction in Settings panel.

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-4651: ------------------------------------------ Hi [~uxdlc] [~porcelli]! All the informations related to the ScenarioSimulation asset are stored inside the "scesim" file. Those informations are both data structure/model *and* settings needed to run the scenario (imported DMN for DMN-related scesim, execution settings, etc). It seems very possible that while the user is editing the data (i.e. whatever is written in the grid) he/she decide to change something in the setting *but* without saving the data. We needed a way - for the user - to separate *settings* saving from *data* saving. As far as we know, the common "Save" button is meant to store everything that is present in the editor to the edited file, so we decided to create a specific button and to give it the required logic. If it is possible to achieve the same result in a different way, we will be happy to implement that. Cheers > 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 > > 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

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

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Elizabeth Clayton reassigned DROOLS-4651: ----------------------------------------- Assignee: (was: Gabriele Cardosi) > 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 > > 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

[JBoss JIRA] (WFCORE-4716) Upgrade Byteman to 4.0.8

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4716: -------------------------------------- Summary: Upgrade Byteman to 4.0.8 Key: WFCORE-4716 URL: https://issues.jboss.org/browse/WFCORE-4716 Project: WildFly Core Issue Type: Component Upgrade Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 11.0.0.Beta2 -- 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 Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Gabriele Cardosi reassigned DROOLS-4651: ---------------------------------------- Assignee: Gabriele Cardosi (was: Toni Rikkola) > 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 > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > 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

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

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4651: ------------------------------------------- [~aglass] [~srambach] If you have any background history on this topic, if you could provide it that would be helpful. Tao worked on this, so I don't have the full history. > 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 > Assignee: Toni Rikkola > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > 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