January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4958) Managing DMN FEEL type classes on KOGITO

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4958: ---------------------------------- Summary: Managing DMN FEEL type classes on KOGITO Key: DROOLS-4958 URL: https://issues.redhat.com/browse/DROOLS-4958 Project: Drools Issue Type: Sub-task Components: Scenario Simulation and Testing Reporter: Yeser Amer Assignee: Yeser Amer -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4957) Adapt ScenarioSimulation Wrapper for Kogito project

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4957: ---------------------------------- Summary: Adapt ScenarioSimulation Wrapper for Kogito project Key: DROOLS-4957 URL: https://issues.redhat.com/browse/DROOLS-4957 Project: Drools Issue Type: Sub-task Reporter: Yeser Amer Assignee: Yeser Amer -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4216) Create runtime and testing version of kogito webapp

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4216?page=com.atlassian.jira.plug... ] Yeser Amer reassigned DROOLS-4216: ---------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Create runtime and testing version of kogito webapp > --------------------------------------------------- > > Key: DROOLS-4216 > URL: https://issues.redhat.com/browse/DROOLS-4216 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > > For each asset there should be two *kogito* webapp: > # a **development/testing** one, that should provide **VS CODE** features, > # a **runtime** one, without the above, to be used inside **VS CODE** > To allow *inheritance* and avoid code-duplication, a common, parent *jar* will also be implemented -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4216) Create runtime and testing version of kogito webapp

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4216?page=com.atlassian.jira.plug... ] Yeser Amer reopened DROOLS-4216: -------------------------------- > Create runtime and testing version of kogito webapp > --------------------------------------------------- > > Key: DROOLS-4216 > URL: https://issues.redhat.com/browse/DROOLS-4216 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > For each asset there should be two *kogito* webapp: > # a **development/testing** one, that should provide **VS CODE** features, > # a **runtime** one, without the above, to be used inside **VS CODE** > To allow *inheritance* and avoid code-duplication, a common, parent *jar* will also be implemented -- 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 Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4249?page=com.atlassian.jira.plug... ] Yeser Amer reopened DROOLS-4249: -------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > 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 > > 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-4950) Different behavior of collection unary checks

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4950: ------------------------------------- I think it is crucial to explain this difference directly in the popup, somewhere close to radio buttons create/define. > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4950: ------------------------------------ [~jomarko] I asked to [~danielezonca] ragarding this behavior, and I confirm you this is the expected one, because, in case of Graphical editor, EXPECTED collections works like a "contains" and not like an "equals". For example, If you try to put ?=[4] in the first row you will receive an error. In the case of an expression defined collection, it works like an "equals". I agree this is not clear and maybe it should be documented in some way (I didn't know it too). > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4920) Scenario simulation for DMN with collections throws en error

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4920?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4920: ------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Scenario simulation for DMN with collections throws en error > ------------------------------------------------------------ > > Key: DROOLS-4920 > URL: https://issues.redhat.com/browse/DROOLS-4920 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-08 14-14-05.png, urgent.dmn > > > If a user tries to create a test scenario for [^urgent.dmn] he will get a [1] even when he is creating test scenario for the first time. > [1] > !Screenshot from 2020-01-08 14-14-05.png|thumbnail! > h3. Acceptance criteria > https://github.com/jboss-integration/bxms-qe-tests/pull/3048 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12999) EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/WFLY-12999?page=com.atlassian.jira.plugi... ] Ricardo Martin Camarero commented on WFLY-12999: ------------------------------------------------ This JIRA is for completing tests for WFCORE issue WFCORE-4803. > EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12999 > URL: https://issues.redhat.com/browse/WFLY-12999 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 19.0.0.Beta1 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > > Modify the test SaslLegacyMechanismConfigurationTestCase to include a test that configures {{DIGEST-MD5}} in the {{SASL_MECHANISMS}} option. > Test for core issue: https://issues.redhat.com/browse/WFCORE-4803 > Although a test in WFCORE was included it's better if this configuration is also tested in the real remoting/EJB scenario. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12999) EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test

by Ricardo Martin Camarero (Jira)

Ricardo Martin Camarero created WFLY-12999: ---------------------------------------------- Summary: EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test Key: WFLY-12999 URL: https://issues.redhat.com/browse/WFLY-12999 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 19.0.0.Beta1 Reporter: Ricardo Martin Camarero Assignee: Ricardo Martin Camarero Modify the test SaslLegacyMechanismConfigurationTestCase to include a test that configures {{DIGEST-MD5}} in the {{SASL_MECHANISMS}} option. Test for core issue: https://issues.redhat.com/browse/WFCORE-4803 Although a test in WFCORE was included it's better if this configuration is also tested in the real remoting/EJB scenario. -- 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 January 2020