June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4446) Confusing scenario validation message for collection types

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4446?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4446: ------------------------------------ Hi [~jomarko], I just checked with master version, and the current error is: *string* changed to *LKW* (screenshot is attached) Considering this, I think we can close this ticket, WDYT? > Confusing scenario validation message for collection types > ---------------------------------------------------------- > > Key: DROOLS-4446 > URL: https://issues.redhat.com/browse/DROOLS-4446 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.26.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2019-08-20 10-19-46.png, Screenshot from 2020-06-10 16-24-49.png > > > There is small enhancement needed if the user validates dmn scenario with *collection* data type, being previously simple data type. > h2. Steps to reproduce > - Create new DMN > - Define there custom data type *LKW:string* > - Set this LKW type for some *input data* node > - Save DMN > - Create a Scenario for this DMN > - Go back to DMN > - Check tickbox *Is Collection* for the *LKW* type > - Save DMN > - Validate Scenario, you will get message as shown in the picture. It can be confusing as it says *LKW* changed to *LKW* -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4446) Confusing scenario validation message for collection types

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4446?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4446: ------------------------------- Attachment: Screenshot from 2020-06-10 16-24-49.png > Confusing scenario validation message for collection types > ---------------------------------------------------------- > > Key: DROOLS-4446 > URL: https://issues.redhat.com/browse/DROOLS-4446 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.26.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2019-08-20 10-19-46.png, Screenshot from 2020-06-10 16-24-49.png > > > There is small enhancement needed if the user validates dmn scenario with *collection* data type, being previously simple data type. > h2. Steps to reproduce > - Create new DMN > - Define there custom data type *LKW:string* > - Set this LKW type for some *input data* node > - Save DMN > - Create a Scenario for this DMN > - Go back to DMN > - Check tickbox *Is Collection* for the *LKW* type > - Save DMN > - Validate Scenario, you will get message as shown in the picture. It can be confusing as it says *LKW* changed to *LKW* -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5384) Clicking rightmost column's header in DMN decision table raises an error

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5384?page=com.atlassian.jira.plug... ] Daniel José dos Santos commented on DROOLS-5384: ------------------------------------------------ [~tkobayashi], I reproduced the error now with that information that the grid was scrolled. I didn't noticed that at the first place. The fix is made and I'm ready to send the PR, I think we can reopen this Jira and sent the PR. Can I reopen this JIRA? [~jomarko] > Clicking rightmost column's header in DMN decision table raises an error > ------------------------------------------------------------------------ > > Key: DROOLS-5384 > URL: https://issues.redhat.com/browse/DROOLS-5384 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.39.0.Final > > Attachments: dmn-decision-table-error-popup-7.38.0.png, drools5384.mp4 > > > When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (At the first time, it raises an error popup. After that, the header is unresponsive) > See screenshot. > Chrome 80.0.3987.122 > Firefox 60.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5384) Clicking rightmost column's header in DMN decision table raises an error

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5384?page=com.atlassian.jira.plug... ] Daniel José dos Santos commented on DROOLS-5384: ------------------------------------------------ Hi! If I'm not wrong, the last column should be empty because now user can set the header of the column. If we fixed the column with "Description", then we'll have to save that information in the DMN file or prevent user to edit the header. We can change the "Enter text" to "Description". With the DMN 1.2 user can add N columns now and set different titles for each one. [~manstis] [~jomarko] > Clicking rightmost column's header in DMN decision table raises an error > ------------------------------------------------------------------------ > > Key: DROOLS-5384 > URL: https://issues.redhat.com/browse/DROOLS-5384 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.39.0.Final > > Attachments: dmn-decision-table-error-popup-7.38.0.png, drools5384.mp4 > > > When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (At the first time, it raises an error popup. After that, the header is unresponsive) > See screenshot. > Chrome 80.0.3987.122 > Firefox 60.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4582) Cell selection doesn't span the entire cell if you Insert RightMost Column

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4582?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4582: ------------------------------- Story Points: 1 > Cell selection doesn't span the entire cell if you Insert RightMost Column > -------------------------------------------------------------------------- > > Key: DROOLS-4582 > URL: https://issues.redhat.com/browse/DROOLS-4582 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: CustomerFocus, drools-tools > Attachments: image-2019-10-01-10-50-42-411.png > > > !image-2019-10-01-10-50-42-411.png|thumbnail! > Selection doesn't span entirely if you bind new column -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4582) Cell selection doesn't span the entire cell if you Insert RightMost Column

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4582?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4582: ------------------------------- Sprint: 2020 Week 22-24 (from May 25) > Cell selection doesn't span the entire cell if you Insert RightMost Column > -------------------------------------------------------------------------- > > Key: DROOLS-4582 > URL: https://issues.redhat.com/browse/DROOLS-4582 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: CustomerFocus, drools-tools > Attachments: image-2019-10-01-10-50-42-411.png > > > !image-2019-10-01-10-50-42-411.png|thumbnail! > Selection doesn't span entirely if you bind new column -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-108) Upgrade Infinispan Core to 9.3.9.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELYWEB-108?page=com.atlassian.jira.plugi... ] Farah Juma updated ELYWEB-108: ------------------------------ Fix Version/s: (was: 1.7.2.CR1) > Upgrade Infinispan Core to 9.3.9.Final > -------------------------------------- > > Key: ELYWEB-108 > URL: https://issues.redhat.com/browse/ELYWEB-108 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.8.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4998) Upgrade WildFly Common to 1.5.2.Final

by Ingo Weiss (Jira)

Ingo Weiss created WFCORE-4998: ---------------------------------- Summary: Upgrade WildFly Common to 1.5.2.Final Key: WFCORE-4998 URL: https://issues.redhat.com/browse/WFCORE-4998 Project: WildFly Core Issue Type: Component Upgrade Reporter: Ingo Weiss Assignee: Darran Lofthouse Fix For: 11.0.0.Beta1, 11.0.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1975) Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1975?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1975: ---------------------------------- Fix Version/s: 1.13.0.CR1 > Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder > ----------------------------------------------------------------------------------------------------- > > Key: ELY-1975 > URL: https://issues.redhat.com/browse/ELY-1975 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.13.0.CR1 > > > {{AcmeClientSpi#obtainCertificate}} currently determines the order URL that should be used by taking the {{Location}} header from the response to finalizing the order (the ACME protocol specification has an example response that includes this header). This works when obtaining certificates from Let's Encrypt and Boulder. However, it seems that EJBCA does not include the {{Location}} header in the response to finalizing the order. {{AcmeClientSpi#obtainCertificate}} should instead use the Location header from the response to {{newOrder}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1975) Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1975?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved ELY-1975. ----------------------------------- Resolution: Done > Update AcmeClientSpi#obtainCertificate so that it obtains the order URL from the response to newOrder > ----------------------------------------------------------------------------------------------------- > > Key: ELY-1975 > URL: https://issues.redhat.com/browse/ELY-1975 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.13.0.CR1 > > > {{AcmeClientSpi#obtainCertificate}} currently determines the order URL that should be used by taking the {{Location}} header from the response to finalizing the order (the ACME protocol specification has an example response that includes this header). This works when obtaining certificates from Let's Encrypt and Boulder. However, it seems that EJBCA does not include the {{Location}} header in the response to finalizing the order. {{AcmeClientSpi#obtainCertificate}} should instead use the Location header from the response to {{newOrder}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020