June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5282) Client side FEEL

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5282?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5282: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > Client side FEEL > ---------------- > > Key: DROOLS-5282 > URL: https://issues.redhat.com/browse/DROOLS-5282 > Project: Drools > Issue Type: Epic > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Make kie-dmn-feel usable in the client side. > Notes: > * FEEL functions use reflection, but many if not all of them can be hard coded -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5262) java.lang.Number import remains in the list of imports after deletion

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5262?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5262: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > java.lang.Number import remains in the list of imports after deletion > --------------------------------------------------------------------- > > Key: DROOLS-5262 > URL: https://issues.redhat.com/browse/DROOLS-5262 > Project: Drools > Issue Type: Bug > Affects Versions: 7.37.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Optional > Labels: drools-tools > Attachments: Screenshot from 2018-01-09 12-56-56.png > > > When you delete java.lang.Number from project's imports in the business central and you create some asset in this project, java.lang.Number is still present in External imports of the created asset. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5259) DMN Validation takes 15s in the BC while the same file takes half a second as an unit test

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5259?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5259: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > DMN Validation takes 15s in the BC while the same file takes half a second as an unit test > ------------------------------------------------------------------------------------------ > > Key: DROOLS-5259 > URL: https://issues.redhat.com/browse/DROOLS-5259 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Problem might be related to some limitation with Wildfly. It felt even slower with drools-wb-showcase, but need to time it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5232) Improve DMNDI validation rule

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5232?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5232: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > Improve DMNDI validation rule > ----------------------------- > > Key: DROOLS-5232 > URL: https://issues.redhat.com/browse/DROOLS-5232 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > Improve DMNDI validation rule not to use eval function. > Idea: Add a static java function which takes Definitions and will produce as output all descendant children. So we can write a rule to get them by single "from". > https://github.com/kiegroup/drools/pull/2839#discussion_r405998284 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5229) DMNValidate mojo fails XMLSchema validation with included models

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5229?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5229: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > DMNValidate mojo fails XMLSchema validation with included models > ---------------------------------------------------------------- > > Key: DROOLS-5229 > URL: https://issues.redhat.com/browse/DROOLS-5229 > Project: Drools > Issue Type: Bug > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: ValidateDMN Mojo Failure.png, xml_validation_error.zip > > > The attached DMN decision project was built using Business Central 7.34.0.Final. In this project, the dmn model `Math Functions.dmn` invokes business knowledge model `Quotient` from dmn model `Divide.dmn`. Invoking the ValidateDMN mojo (enabled by default) from the kie-maven-plugin fails XML Validation. One can get past this error by disabling DMNValidation with the following configuration in the pom (though disabling DMNValidation for an XML Schema validation also prevents finding FEEL parser errors): > ``` > <build> > <plugins> > <plugin> > <groupId>org.kie</groupId> > <artifactId>kie-maven-plugin</artifactId> > <version>7.34.0.Final</version> > <extensions>true</extensions> >  > <configuration> > <validateDMN>disabled</validateDMN> > </configuration> > </plugin> > </plugins> > </build> > ``` > When one combines the two dmn models into a single model, the XML Validation succeeds (this example is not supplied, but is trivial to re-build). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5203: ----------------------------------- Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5240) Remove MVEL from Drools

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5240?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5240: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > Remove MVEL from Drools > ----------------------- > > Key: DROOLS-5240 > URL: https://issues.redhat.com/browse/DROOLS-5240 > Project: Drools > Issue Type: Epic > Components: core engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Labels: MDP_BRAINFARTS > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5101) rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5101?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5101: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError > -------------------------------------------------------------------------- > > Key: DROOLS-5101 > URL: https://issues.redhat.com/browse/DROOLS-5101 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.26.0.Final > Reporter: Charles Herrick > Assignee: Toni Rikkola > Priority: Critical > > 09:13:02,818 ERROR [org.kie.workbench.common.services.backend.builder.core.Builder] (default task-95) GC overhead limit exceeded: java.lang.OutOfMemoryError: GC overhead limit exceeded > 09:13:05,335 ERROR [stderr] (default task-95) java.lang.OutOfMemoryError: GC overhead limit exceeded -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4865: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > Add i18n reporting for DMN V&V > ------------------------------ > > Key: DROOLS-4865 > URL: https://issues.redhat.com/browse/DROOLS-4865 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5193) Implement Listener mechanism to trace execution

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5193?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5193: ----------------------------------- Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)) > Implement Listener mechanism to trace execution > ----------------------------------------------- > > Key: DROOLS-5193 > URL: https://issues.redhat.com/browse/DROOLS-5193 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Implement Listener architecture so that model-implementation may "publish" execution step detail to be read by "listening" code. > Implementation should not be mandatory, i.e. model should not be forced to implement it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020