July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi edited comment on DROOLS-5517 at 7/19/20 10:22 PM: --------------------------------------------------------------------- Ideas: - Add a method to get OutputSet from DMNContext impl (and want isTypeSafe() method in Interface) - Option A) -- Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency -- DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance -- DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity - Option B) -- Map and Recreate DMNContext right before returning evaluateXXX(). [https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core...] was (Author: tkobayashi): Ideas: - Add a method to get OutputSet from DMNContext - Option A) -- Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency -- DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance -- DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity - Option B) -- Map and Recreate DMNContext right before returning evaluateXXX(). https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core... > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi edited comment on DROOLS-5517 at 7/19/20 10:22 PM: --------------------------------------------------------------------- Ideas: - Add a method to get OutputSet from DMNContext impl (and want isTypeSafe() method in Interface?) - Option A) -- Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency -- DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance -- DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity - Option B) -- Map and Recreate DMNContext right before returning evaluateXXX(). [https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core...] was (Author: tkobayashi): Ideas: - Add a method to get OutputSet from DMNContext impl (and want isTypeSafe() method in Interface) - Option A) -- Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency -- DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance -- DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity - Option B) -- Map and Recreate DMNContext right before returning evaluateXXX(). [https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core...] > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi edited comment on DROOLS-5517 at 7/19/20 10:21 PM: --------------------------------------------------------------------- Ideas: - Add a method to get OutputSet from DMNContext - Option A) -- Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency -- DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance -- DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity - Option B) -- Map and Recreate DMNContext right before returning evaluateXXX(). https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core... was (Author: tkobayashi): Ideas: - Add a method to get OutputSet from DMNContext Option A) - Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency - DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance - DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity Option B) - Map and Recreate DMNContext right before returning evaluateXXX(). https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core... > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5517: ------------------------------------------- Ideas: - Add a method to get OutputSet from DMNContext Option A) - Share DMNContextFPAImpl for both InputSet and OutputSet for clone() consistency - DMNContextFPAImpl.clone() will return DMNContextFPAImpl instance - DMNContextFPAImpl will delegate operations to DMNContextImpl in order to avoid complexity Option B) - Map and Recreate DMNContext right before returning evaluateXXX(). https://github.com/kiegroup/drools/blob/7.40.0.Final/kie-dmn/kie-dmn-core... > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5517: ----------------------------------------- Summary: Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet Key: DROOLS-5517 URL: https://issues.redhat.com/browse/DROOLS-5517 Project: Drools Issue Type: Enhancement Components: dmn engine Affects Versions: 7.40.0.Final Reporter: Toshiya Kobayashi Assignee: Matteo Mortari DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-5517: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Matteo Mortari) > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ] Richard Achmatowicz edited comment on WFLY-13433 at 7/19/20 6:22 PM: --------------------------------------------------------------------- Completed one of the more tricky resources, EJBRemoteResourceDefinition. See: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433|https://github.co...] was (Author: rachmato): Completed one of the more tricky resources, EJBRemoteResourceDefinition. See: https://github.com/rachmatowicz/wildfly/tree/WFLY-13433-remote > Improve capability support in EJB3 subsystem > -------------------------------------------- > > Key: WFLY-13433 > URL: https://issues.redhat.com/browse/WFLY-13433 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 20.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > > Survey all external subsystem dependencies and introduce capability based dependencies where required. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ] Richard Achmatowicz edited comment on WFLY-13433 at 7/19/20 3:22 PM: --------------------------------------------------------------------- Two more resources: {noformat} EJB3IIOPResourceDefinition RemotingProfileResourceDefinition {noformat} >From my notes, these are all of the resources defined in the EJB3 subsystem. There are two cases where I did not add/make use of capability references and left legacy service names in place: * when an EJB3 subsystem makes use of an external dependency from subsystem EXT but subsystem EXT has not been converted to use capabilities (there are a number of these...transactions, IIOP, Service module loader, ... ) * when the service names referenced are associated with deployment-specific services internal to the EJB3 subsystem This could benefit from a review as it's likely I have missed some things. I'll review myself in a day or two. The -DallTests testsuite passes locally. was (Author: rachmato): Two more resources: {noformat} EJB3IIOPResourceDefinition RemotingProfileResourceDefinition {noformat} >From my notes, these are all of the resources defined in the EJB3 subsystem. There are two cases where I did not add/make use of capability references and left legacy service names in place: * when an EJB3 subsystem makes use of an external dependency from subsystem EXT but subsystem EXT has not been converted to use capabilities (there are a number of these...transactions, IIOP, Service module loader, ... ) * when the service names referenced are associated with deployment-specific services internal to the EJB3 subsystem This could benefit from a review as it's likely I have missed some things. I'll review myself in a day or two. > Improve capability support in EJB3 subsystem > -------------------------------------------- > > Key: WFLY-13433 > URL: https://issues.redhat.com/browse/WFLY-13433 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 20.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > > Survey all external subsystem dependencies and introduce capability based dependencies where required. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13575) Remove all hard coded references to Artemis default values

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13575?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13575: ------------------------------------------ Mismatch is not an issue, those are values that might be there because of retro compatibility that we don't want to change. > Remove all hard coded references to Artemis default values > ---------------------------------------------------------- > > Key: WFLY-13575 > URL: https://issues.redhat.com/browse/WFLY-13575 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 20.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Michal Petrov > Priority: Major > > There are still attributes that use Artemis default configuration valuues from FileConfiguration for example. > Remove those values so that they are not updated behind the scene and add a test to know when our default values don't align with Artemis ones. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5516) Date field in Guided rule template is not displaying correct date

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-5516: ------------------------------------ Summary: Date field in Guided rule template is not displaying correct date Key: DROOLS-5516 URL: https://issues.redhat.com/browse/DROOLS-5516 Project: Drools Issue Type: Bug Components: Guided Template Editor Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 July 2020