June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4042: ---------------------------------------- [~tirelli] Ah, OK.. enhancement tracked https://issues.jboss.org/browse/DROOLS-4195 > [DMN Designer] Add support for importing and consuming PMML models 7.5 > ---------------------------------------------------------------------- > > Key: DROOLS-4042 > URL: https://issues.jboss.org/browse/DROOLS-4042 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.24.0.Final > > > We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor. > h2. Requirement > - As user, via included models tab, remove included pmml model, even if used somewhere > - As user, via included models tab, rename included pmml model, even if used somewhere > - As user, via included models tab, include multiple pmml models > - As user, via included models tab, include multiple pmml models at the same time eternal dmn > - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished > - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values > - As user, via included models tab, no restriction for included pmml model name > - As user, via new test scenarios, test dmn model that uses pmml inside > - As user, via kie-server, query kie container that has dmn model with pmml > - As user, via included models tab, I want to have just unique aliases of imported models > h2. UX design > - Selectbox in place of Document and Model selection > h2. Documentation > - Mention what pmml model can be imported into dmn > - Mention where it can be used > - Mention if something more needed to dpeloy such project on kie server > h2. Acceptance test > - Include two pmml models > - In dmn, select one in function grid > - Change the selected one to second > - Finish the dmn model > - build deploy on kie-server > - Interact with kie container via rest > - Create new test scenario for created dmn model > - In included models tab, try to include one pmml and one dmn with same alias, it shouldn't be possible -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4195: ----------------------------------- Reporter: Edson Tirelli (was: Michael Anstis) > [DMN Designer] PMML: Update Document value when Import alias changes > -------------------------------------------------------------------- > > Key: DROOLS-4195 > URL: https://issues.jboss.org/browse/DROOLS-4195 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > When a PMML document is imported it is given an alias. > When the PMML document is used in a {{Function}} the alias is used as the document name. > When the import alias is changed {{Function}}s referencing the old alias should be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4196) [DMN Designer] PMML: Show default when document has no explicit model

by Michael Anstis (Jira)

Michael Anstis created DROOLS-4196: -------------------------------------- Summary: [DMN Designer] PMML: Show default when document has no explicit model Key: DROOLS-4196 URL: https://issues.jboss.org/browse/DROOLS-4196 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.24.0.Final Reporter: Edson Tirelli Assignee: Michael Anstis If the PMML file contains no "named" model (only an anonymous one), the UI should indicate that this model is being used (how to indicate that I leave to UX, but we can call it "default model" or whatever). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes

by Michael Anstis (Jira)

Michael Anstis created DROOLS-4195: -------------------------------------- Summary: [DMN Designer] PMML: Update Document value when Import alias changes Key: DROOLS-4195 URL: https://issues.jboss.org/browse/DROOLS-4195 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.24.0.Final Reporter: Michael Anstis Assignee: Michael Anstis When a PMML document is imported it is given an alias. When the PMML document is used in a {{Function}} the alias is used as the document name. When the import alias is changed {{Function}}s referencing the old alias should be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-783) Review and Create new Kiali Install/Deploy Test Cases

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-783?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-783: ---------------------------------- Sprint: Kiali Sprint #23, Kiali Sprint #24 (was: Kiali Sprint #23) > Review and Create new Kiali Install/Deploy Test Cases > ----------------------------------------------------- > > Key: SWSQE-783 > URL: https://issues.jboss.org/browse/SWSQE-783 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: pqi > > Currently there is 1 Polarion Install test case. Review this test case and separate into multiple test cases, as needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-782) Map Jira Queries to Tablue Graphs

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-782?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-782: ---------------------------------- Sprint: Kiali Sprint #23, Kiali Sprint #24 (was: Kiali Sprint #23) > Map Jira Queries to Tablue Graphs > --------------------------------- > > Key: SWSQE-782 > URL: https://issues.jboss.org/browse/SWSQE-782 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Prachi Yadav > Priority: Major > Labels: pqi > > Map Jira Query to Tableau Graphs, so that we can then validate that the Jira queries are correct. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-736) Create OCP4.1 Cluster on Bare Metal

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-736?page=com.atlassian.jira.plugin.... ] Matthew Mahoney closed SWSQE-736. --------------------------------- Release Notes Text: No longer relevant. Resolution: Done > Create OCP4.1 Cluster on Bare Metal > ------------------------------------ > > Key: SWSQE-736 > URL: https://issues.jboss.org/browse/SWSQE-736 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > OC4.1 now supports bare metal. > https://github.com/openshift/installer/releases -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-608) QE CI/CP Integration - stage 1

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-608?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-608: ---------------------------------- Sprint: Kiali Sprint #18, Kiali Sprint #23, Kiali Sprint #24 (was: Kiali Sprint #18, Kiali Sprint #23) > QE CI/CP Integration - stage 1 > ------------------------------ > > Key: SWSQE-608 > URL: https://issues.jboss.org/browse/SWSQE-608 > Project: Kiali QE > Issue Type: Story > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > 90 Day QE CI/CP Integration Goals as defined in https://docs.google.com/document/d/13rp2_oEN2fKIskzuqtGB64zWPGBGQR50yMVBU... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12194) Add a testcase that checks remote client transaction afinity in case of failed server

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-12194?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated WFLY-12194: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12370 > Add a testcase that checks remote client transaction afinity in case of failed server > ------------------------------------------------------------------------------------- > > Key: WFLY-12194 > URL: https://issues.jboss.org/browse/WFLY-12194 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 17.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The remote client transaction affinity is not well covered in testsuite. > Particularly, it would be good to test what happens when a transaction starts on a standalone client. The call goes to a stateless bean. There are two servers started in server that the client can choose. The client starts transaction, calls the bean and then the server fails. Will be the next call to bean fails correctly? (as it could be expected as the affinity points to the non-existent server, despite the fact there is another server deploying the same stateless bean) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12194) Add a testcase that checks remote client transaction afinity in case of failed server

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-12194?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka commented on WFLY-12194: ----------------------------------------- Based on the investigation of behaviour described in the documentation (see https://issues.jboss.org/browse/JBEAP-16879) adding new testcases working with EJB remoting protocols and transaction affinity. > Add a testcase that checks remote client transaction afinity in case of failed server > ------------------------------------------------------------------------------------- > > Key: WFLY-12194 > URL: https://issues.jboss.org/browse/WFLY-12194 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 17.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The remote client transaction affinity is not well covered in testsuite. > Particularly, it would be good to test what happens when a transaction starts on a standalone client. The call goes to a stateless bean. There are two servers started in server that the client can choose. The client starts transaction, calls the bean and then the server fails. Will be the next call to bean fails correctly? (as it could be expected as the affinity points to the non-existent server, despite the fact there is another server deploying the same stateless bean) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019