April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3892) DMN (DEV): Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3892?page=com.atlassian.jira.plugi... ] Elizabeth Clayton reassigned DROOLS-3892: ----------------------------------------- Assignee: Guilherme Gomes (was: Elizabeth Clayton) > DMN (DEV): Add a nested row to a new Structured data type by default > -------------------------------------------------------------------- > > Key: DROOLS-3892 > URL: https://issues.jboss.org/browse/DROOLS-3892 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability: Reduce the number of clicks / actions to add a nested element. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3892) DMN (DEV): Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-3892: ----------------------------------------- Summary: DMN (DEV): Add a nested row to a new Structured data type by default Key: DROOLS-3892 URL: https://issues.jboss.org/browse/DROOLS-3892 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Elizabeth Clayton Assignee: Elizabeth Clayton Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png Usability: Reduce the number of clicks / actions to add a nested element. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)

by ziad saade (Jira)

[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ] ziad saade commented on WFLY-11116: ----------------------------------- Hi Paul I did another workaround to fix the issue; the fix is at the level of JS/HTML; instead of submitting the form through an onClick event that calls a JS Function (form.submit()), I submitted the form through submit button with form "method" and "action" tags, does the above have any relationship with WildFly issues since the same is not reproduced on many other Application Servers? is it possible to have a fix? PS: if you need further details don't hesitate to contact me. Thanks for usual support. Best Regards (Restricted to jira-users group) > Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception) > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11116 > URL: https://issues.jboss.org/browse/WFLY-11116 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final, 15.0.0.Final > Reporter: ziad saade > Assignee: Paul Ferraro > Priority: Critical > > I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow: > > Book.java > TestBean testBean=null; > if(session.getAttribute("testBean")!=null) > testBean = (TestBean)session.getAttribute("testBean"); > else{ > testBean=new TestBean(); > session.setAttribute("testBean",testBean); > } > testBean.setAmount("10"); > > response.sendRedirect("BookPreview"); > > > The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated. > > BookPreview.java > > TestBean testBean = (TestBean)session.getAttribute("testBean"); > String amount = testBean.getAmount; //Null pointer exception when submitting the form > > <form method="Post" action="BookPreview"> > > </form> > > TestBean.java > > public class TestBean implements java.io.Serializable { > > private static final long serialVersionUID = 1L; > private String amount; > > public String getAmount() { > return amount; > } > > public void setAmount(String amount) { > this.amount = amount; > } > } > > Kindly advice how to fix the problem at the level of the server configuration. > PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....) > > Thanks and Best Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-716) PQI reports for TP10 - Test cases quality audit reports and approvals

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-716?page=com.atlassian.jira.plugin.... ] Sunil Kondkar reassigned SWSQE-716: ----------------------------------- Assignee: Sunil Kondkar > PQI reports for TP10 - Test cases quality audit reports and approvals > --------------------------------------------------------------------- > > Key: SWSQE-716 > URL: https://issues.jboss.org/browse/SWSQE-716 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > There are two test runs to be tagged for TP10. Below are the tasked that needs to be performed so that they are ready for PQI reports. > -Test case quality audit report shows around 24 test cases which does not have automated scripts mentioned. > https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > -Approve all test cases in all test runs so that they will be included in PQI reports -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-716) PQI reports for TP10 - Test cases quality audit reports and approvals

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-716?page=com.atlassian.jira.plugin.... ] Sunil Kondkar updated SWSQE-716: -------------------------------- Sprint: Kiali Sprint #21 > PQI reports for TP10 - Test cases quality audit reports and approvals > --------------------------------------------------------------------- > > Key: SWSQE-716 > URL: https://issues.jboss.org/browse/SWSQE-716 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Priority: Major > Labels: pqi > > There are two test runs to be tagged for TP10. Below are the tasked that needs to be performed so that they are ready for PQI reports. > -Test case quality audit report shows around 24 test cases which does not have automated scripts mentioned. > https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > -Approve all test cases in all test runs so that they will be included in PQI reports -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-716) PQI reports for TP10 - Test cases quality audit reports and approvals

by Sunil Kondkar (Jira)

Sunil Kondkar created SWSQE-716: ----------------------------------- Summary: PQI reports for TP10 - Test cases quality audit reports and approvals Key: SWSQE-716 URL: https://issues.jboss.org/browse/SWSQE-716 Project: Kiali QE Issue Type: QE Task Reporter: Sunil Kondkar There are two test runs to be tagged for TP10. Below are the tasked that needs to be performed so that they are ready for PQI reports. -Test case quality audit report shows around 24 test cases which does not have automated scripts mentioned. https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... -Approve all test cases in all test runs so that they will be included in PQI reports -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4428) Upgrade CLI to use aesh 2.4

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4428: -------------------------------------------- Summary: Upgrade CLI to use aesh 2.4 Key: WFCORE-4428 URL: https://issues.jboss.org/browse/WFCORE-4428 Project: WildFly Core Issue Type: Component Upgrade Components: CLI Reporter: Jean Francois Denise Assignee: Jean Francois Denise aesh, aesh-readline and aesh-extensions have been released with http repositories to resolve artifacts, it needs a new release. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3439?page=com.atlassian.jira.plugi... ] Gabriele Cardosi edited comment on DROOLS-3439 at 4/16/19 7:17 AM: ------------------------------------------------------------------- [~kkufova] I understood the overall goal - it is not exactly clear the expected behavior: 1) what should happen if the user click on any of the "un-selectable" cells? If - for ex - the user selected a valid cell , and then click on an invalid one, should the previous one kept selected ? 2) It seems (please correct me if I'm wrong) that selection changes with arrow keys (up/down/left/right); what should happen when the key move the "cursor" over an un-selectable cell? Should the previous one kept selected ? 3) if a final user uses the key and moves to an un-selectable cell, how does he/she may know where the "cursor" currently is ? 4) currently, by default, at scenario loading the top left cell (the "#") get selected: is this behavior to be kept ? was (Author: gabriolo): [~kkufova] I understood the overall goal - it is not exactly clear the expected behavior: 1) what should happen if the user click on any of the "un-selectable" cells? If - for ex - the user selected a valid cell , and then click on an invalid one, should the previous one kept selected ? 2) It seems (please correct me if I'm wrong) that selection changes with arrows key (up/down/left/right); what should happen when the key move the "cursor" over an un-selectable cell? Should the previous one kept selected ? 3) if a final user uses the key and moves to an un-selectable cell, how does he may know where he/she currently is ? 4) currently, by default, at scenario loading the top left cell (the "#") get selected: is this behavior to be kept ? > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.jboss.org/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3439?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3439: ------------------------------------------ [~kkufova] I understood the overall goal - it is not exactly clear the expected behavior: 1) what should happen if the user click on any of the "un-selectable" cells? If - for ex - the user selected a valid cell , and then click on an invalid one, should the previous one kept selected ? 2) It seems (please correct me if I'm wrong) that selection changes with arrows key (up/down/left/right); what should happen when the key move the "cursor" over an un-selectable cell? Should the previous one kept selected ? 3) if a final user uses the key and moves to an un-selectable cell, how does he may know where he/she currently is ? 4) currently, by default, at scenario loading the top left cell (the "#") get selected: is this behavior to be kept ? > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.jboss.org/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3439?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3439: --------------------------------- Attachment: table.png > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.jboss.org/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 April 2019