February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5037) Create kogito-client module

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5037?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5037: -------------------------------- Tester: Jozef Marko > Create kogito-client module > --------------------------- > > Key: DROOLS-5037 > URL: https://issues.redhat.com/browse/DROOLS-5037 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4249?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4249: ------------------------------------- [~yamer] the description says a prototype, does it mean marshalling just of some classes? > 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, 3 months

1
0
0 / 0

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

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4249?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4249: -------------------------------- Labels: drools-tools (was: ) > 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, 3 months

1
0
0 / 0

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

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4249?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4249: -------------------------------- Tester: Jozef Marko > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4172) Add support for TLS 1.3

by Harish Murali (Jira)

[ https://issues.redhat.com/browse/WFCORE-4172?page=com.atlassian.jira.plug... ] Harish Murali edited comment on WFCORE-4172 at 2/12/20 6:29 AM: ---------------------------------------------------------------- [~fjuma] [~jstourac] Can you let me know the wildfly version from where this is available. I can see only the elytron version here. Is this available only in wildfly 19? We are using wildfly version 17. If I manually merge this commit to wildfly 17 (only locally), what are the chances that it is going to work there. was (Author: harishjboss1): [~fjuma] Can you let me know the wildfly version from where this is available. I can see only the elytron version here. Is this available only in wildfly 19? We are using wildfly version 17. If I manually merge this commit to wildfly 17 (only locally), what are the chances that it is going to work there. > Add support for TLS 1.3 > ----------------------- > > Key: WFCORE-4172 > URL: https://issues.redhat.com/browse/WFCORE-4172 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: affects-model, eap-7.2.0-deferred > Fix For: 11.0.0.Beta6 > > > It presently appears as though TLS 1.3 support could be available from Java 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5055) We are currently migrating our project from 6.5.0.Final-redhat-25 to 7.x and struggling with a breaking change

by Enrique González Martínez (Jira)

[ https://issues.redhat.com/browse/DROOLS-5055?page=com.atlassian.jira.plug... ] Enrique González Martínez updated DROOLS-5055: ---------------------------------------------- Attachment: drools-alpha-expired-event.zip > We are currently migrating our project from 6.5.0.Final-redhat-25 to 7.x and struggling with a breaking change > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5055 > URL: https://issues.redhat.com/browse/DROOLS-5055 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Enrique González Martínez > Assignee: Luca Molteni > Priority: Major > Fix For: 7.32.0.Final > > Attachments: drools-alpha-expired-event.zip > > > if you run the test you have modified: > in 6.5.0-Final it gives you: > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 > SUCCESS > in 7.26.0-Final (and above): > Tests run: 3, Failures: 3, Errors: 0, Skipped: 0 > which means that there is a *breaking change issue between 6.5.0-Final and >7.26.0-Final * -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5055) We are currently migrating our project from 6.5.0.Final-redhat-25 to 7.x and struggling with a breaking change

by Enrique González Martínez (Jira)

Enrique González Martínez created DROOLS-5055: ------------------------------------------------- Summary: We are currently migrating our project from 6.5.0.Final-redhat-25 to 7.x and struggling with a breaking change Key: DROOLS-5055 URL: https://issues.redhat.com/browse/DROOLS-5055 Project: Drools Issue Type: Bug Components: core engine Reporter: Enrique González Martínez Assignee: Luca Molteni Fix For: 7.32.0.Final if you run the test you have modified: in 6.5.0-Final it gives you: Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 SUCCESS in 7.26.0-Final (and above): Tests run: 3, Failures: 3, Errors: 0, Skipped: 0 which means that there is a *breaking change issue between 6.5.0-Final and >7.26.0-Final * -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5054) DMN Editor does not cascade allowedValues for Decision Table input

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5054: -------------------------------------- Summary: DMN Editor does not cascade allowedValues for Decision Table input Key: DROOLS-5054 URL: https://issues.redhat.com/browse/DROOLS-5054 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Matteo Mortari Assignee: Michael Anstis Attachments: Traffic Violation (1).dmn Following the Traffic Violation tutorial, e.g.: https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.... Despite {{Violation.Type}} is defined as a constraint enumeration: {code:xml} <dmn:itemComponent id="_D16710C9-F626-4351-ABCE-C7F0A1A82F70" name="Type" isCollection="false"> <dmn:typeRef>string</dmn:typeRef> <dmn:allowedValues kie:constraintType="enumeration" id="_C4AFEF49-331A-4A9F-B9AF-478DB7525008"> <dmn:text>"speed", "parking", "driving under the influence"</dmn:text> </dmn:allowedValues> </dmn:itemComponent> {code} the constraints are not cascaded down to the Decision Table input: {code:xml} <dmn:input id="_CD3B3323-7C98-44CB-802E-F3A52A4364CC"> <dmn:inputExpression id="_621CEBEF-0710-4474-AFC3-D305517A348F" typeRef="string"> <dmn:text>Violation.Type</dmn:text> </dmn:inputExpression> </dmn:input> {code} and this does not allow for the Decision Table static analysis to be perfomed (the static analysis reckognize these values seems to be enumerated, but the decision table column does not list them) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by Hayk Hovsepyan (Jira)

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

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1042) Automate https://github.com/kiali/kiali/issues/1344

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1042?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1042. ----------------------------------- Resolution: Done Merged and running upstream/master tests on Istio latest. > Automate https://github.com/kiali/kiali/issues/1344 > --------------------------------------------------- > > Key: SWSQE-1042 > URL: https://issues.redhat.com/browse/SWSQE-1042 > 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, 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 February 2020