February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4249) Implement client-side marshalling

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4249?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4249: ------------------------------------ [~jomarko] It's an old description. :) > Implement client-side marshalling > --------------------------------- > > Key: DROOLS-4249 > URL: https://issues.redhat.com/browse/DROOLS-4249 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Implement a protoype for client-side marshalling -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5094) KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10

by Charles Herrick (Jira)

Charles Herrick created DROOLS-5094: --------------------------------------- Summary: KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10 Key: DROOLS-5094 URL: https://issues.redhat.com/browse/DROOLS-5094 Project: Drools Issue Type: Bug Components: Test Scenarios Editor Affects Versions: 7.26.0.Final Reporter: Charles Herrick Assignee: Toni Rikkola bug[1]: Once you set the KIE-Base and a KIE-Session in Settings on a Project, subsequent Test Scenario (Legacy) inherit/adopt the KIE-Base and KIE-Session. The run-scenario fails without even running. Workaround: 1. Create and build the Test Scenario (Legacy) 2. Download the Test Scenario (creates an XML file) 3. Edit the XML file to set the Session to : <ksessions> <string>defaultKieSession</string> </ksessions> 4. Delete the Test Scenario from Decision-Manager > Space > Project > Assets. 5. Import Asset > the edited XML file. Now the Test Scenario will run. Bug[2]: In the Settings for a specific Test Scenario (Legacy) the KIE-Base and KIE-Session are NOT editable and can not be changed. To fix this you have to follow the workaround. Versions: Windows 10, rhdm 7 v 7.5.1, EAP v 7.2, Drools: rhdmAdmin (About) == 7.26 Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1074) Automate API Doc https://github.com/kiali/kiali-ui/pull/1667

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1074: ------------------------------------- Summary: Automate API Doc https://github.com/kiali/kiali-ui/pull/1667 Key: SWSQE-1074 URL: https://issues.redhat.com/browse/SWSQE-1074 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5091) purpose and/or howtouse instruction on guided decision tables

by Werner Van Herrewegen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5091?page=com.atlassian.jira.plug... ] Werner Van Herrewegen updated DROOLS-5091: ------------------------------------------ Description: As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. Business people usually only fill in the decision tables so I limit my scope to guided decision tables. I would like to have a read-only copy of the (already existing) overview>comments field at the top of guided decision tables 'model view'. Only if the text box contains something root cause for this demand is that : * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) * some combinations are not allowed * and no way to enforce/prevent the allowed/forbidden combinations * It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data was: As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. Business people usually only fill in the decision tables so I limit my scope to guided decision tables. I would like to have a read-only copy of either the (already existing) overview>comments or overview>description field at the top of guided decision tables 'model view'. Only if the text box contains something root cause for this demand is that : * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) * some combinations are not allowed * and no way to enforce/prevent the allowed/forbidden combinations * It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data > purpose and/or howtouse instruction on guided decision tables > ------------------------------------------------------------- > > Key: DROOLS-5091 > URL: https://issues.redhat.com/browse/DROOLS-5091 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Werner Van Herrewegen > Assignee: Michael Anstis > Priority: Minor > > As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. > Business people usually only fill in the decision tables so I limit my scope to guided decision tables. > I would like to have a read-only copy of the (already existing) overview>comments field at the top of guided decision tables 'model view'. > Only if the text box contains something > root cause for this demand is that : > * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) > * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) > * some combinations are not allowed > * and no way to enforce/prevent the allowed/forbidden combinations > * It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1070) Automate AuthPolicy https://github.com/kiali/kiali/pull/2261

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1070?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1070: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/251 > Automate AuthPolicy https://github.com/kiali/kiali/pull/2261 > ------------------------------------------------------------ > > Key: SWSQE-1070 > URL: https://issues.redhat.com/browse/SWSQE-1070 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5093) mass initial fill of guided decision table

by Werner Van Herrewegen (Jira)

Werner Van Herrewegen created DROOLS-5093: --------------------------------------------- Summary: mass initial fill of guided decision table Key: DROOLS-5093 URL: https://issues.redhat.com/browse/DROOLS-5093 Project: Drools Issue Type: Feature Request Reporter: Werner Van Herrewegen Assignee: Mario Fusco as a rule creator I want to have an option to download an excel grid based on the columns in a guided decision table and have the business fill this using excel and afterwards upload the filled excel as rows in the guided decision table. reasoning: for large mapping tables it would be nice to create the structure of the decision table in business central then get this structure into excel tables then give the business the excel after the business has filled in the values and after validation of the values by IT :-) we import these values as rows in the table. this is common practice for the initial upload of data in a new system. all changes afterwards will happen via business central webapp I know this bypasses data entry validation and should be used with care, though if implemented decently, mass upload data validation can be still be enforced during import. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5092) rules overview screen sorting, filtering on rules attributes and metadata

by Werner Van Herrewegen (Jira)

Werner Van Herrewegen created DROOLS-5092: --------------------------------------------- Summary: rules overview screen sorting, filtering on rules attributes and metadata Key: DROOLS-5092 URL: https://issues.redhat.com/browse/DROOLS-5092 Project: Drools Issue Type: Feature Request Components: tools Reporter: Werner Van Herrewegen Assignee: Mario Fusco as a rule creator I want to have a flexible way to search for rules that have a certain profile. idea reference: Think of the way jira does it. acceptance criteria: * I would like to be able to show a configurable selection of result fields (each field corresponds with 1 column) * the possible fields are * the existing fields in the rule list overview * plus the fields visible in the overview tab when you open a specific rule/fact/test etc * plus rule meta data fields from the rule * plus rule attribute fields from the rule * plus used facts in the rule/test * plus used fact-fields in the rule/test * plus the description field from the rule * I would like to save this 'view' to re-use it later. * I would like to place a filter(think excel filter) on all and any of the columns in the view * I would like to sort the results on any 1 column in the view az-za -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5091) purpose and/or howtouse instruction on guided decision tables

by Werner Van Herrewegen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5091?page=com.atlassian.jira.plug... ] Werner Van Herrewegen updated DROOLS-5091: ------------------------------------------ Description: As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. Business people usually only fill in the decision tables so I limit my scope to guided decision tables. I would like to have a read-only copy of either the (already existing) overview>comments or overview>description field at the top of guided decision tables 'model view'. Only if the text box contains something root cause for this demand is that : * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) * some combinations are not allowed * and no way to enforce/prevent the allowed/forbidden combinations * It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data was: As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. Business people usually only fill in the decision tables so I limit my scope to guided decision tables. I would like to have a read-only copy of either the (already existing) overview>comments or overview>description field at the top of guided decision tables 'model view'. Only if the text box contains something root cause for this demand is that : * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) * some combinations are not allowed * and no way to enforce/prevent the allowed/forbidden combinations It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data > purpose and/or howtouse instruction on guided decision tables > ------------------------------------------------------------- > > Key: DROOLS-5091 > URL: https://issues.redhat.com/browse/DROOLS-5091 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Werner Van Herrewegen > Assignee: Michael Anstis > Priority: Minor > > As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. > Business people usually only fill in the decision tables so I limit my scope to guided decision tables. > I would like to have a read-only copy of either the (already existing) overview>comments or overview>description field at the top of guided decision tables 'model view'. > Only if the text box contains something > root cause for this demand is that : > * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) > * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) > * some combinations are not allowed > * and no way to enforce/prevent the allowed/forbidden combinations > * It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5091) purpose and/or howtouse instruction on guided decision tables

by Werner Van Herrewegen (Jira)

Werner Van Herrewegen created DROOLS-5091: --------------------------------------------- Summary: purpose and/or howtouse instruction on guided decision tables Key: DROOLS-5091 URL: https://issues.redhat.com/browse/DROOLS-5091 Project: Drools Issue Type: Feature Request Components: Guided Decision Table Editor Reporter: Werner Van Herrewegen Assignee: Michael Anstis As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. Business people usually only fill in the decision tables so I limit my scope to guided decision tables. I would like to have a read-only copy of either the (already existing) overview>comments or overview>description field at the top of guided decision tables 'model view'. Only if the text box contains something root cause for this demand is that : * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) * some combinations are not allowed * and no way to enforce/prevent the allowed/forbidden combinations It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-306) Health check response contains default readiness data

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFWIP-306?page=com.atlassian.jira.plugin... ] Fabio Burzigotti closed WFWIP-306. ---------------------------------- Resolution: Rejected > Health check response contains default readiness data > ----------------------------------------------------- > > Key: WFWIP-306 > URL: https://issues.redhat.com/browse/WFWIP-306 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Fabio Burzigotti > Priority: Critical > > Starting from Wildfly 19 Beta 2 and with current feature branch for MP Health upgrade to 2.2 [1], some tests started to fail, reporting unexpected content in JSON response. > When no _readiness_ health check procedures are defined for a given deployment - the returned JSON payload contains a "default" health check readiness object, conventionally named as "ready-deployment." + <archive-name> > The same _does not_ happen when there's just one registered readiness procedure - i.e. when no annotated _liveness_ procedures exist. > This change is not documented in the Analysis document: https://github.com/wildfly/wildfly-proposals/pull/284 > The following example uses an Arquillian deployment with a single HealthCheck implementation with _liveness_ health check procedure. > 1. feature branch [1] > {code} > //health > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > }, > { > "name": "ready-deployment.HealthTest.war", > "status": "UP" > } > ] > } > //live > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > } > ] > } > //ready > { > "status": "UP", > "checks": [ > { > "name": "ready-deployment.HealthTest.war", > "status": "UP" > } > ] > } > {code} > 2. here are the results for the same calls against Wildfly 19 Beta 1: > {code} > //health > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > } > ] > } > //live > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > } > ] > } > //ready > { > "status": "UP", > "checks": [] > } > {code} > [1] > https://github.com/jmesnil/wildfly -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020