July 2020 - jboss-jira - Jboss List Archives

[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), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (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), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4461?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4461: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Use date picker for LocalDate > ----------------------------- > > Key: DROOLS-4461 > URL: https://issues.redhat.com/browse/DROOLS-4461 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > We should use the date picker for LocalDate like we do for Date. > h2. Acceptance test > - Guided rule condition (/) > - Guided rule action (/) > - Guided rule template condition (/) > - Guided rule template action (/) > - Guided decision table simple condition (/) > - Guided decision table BRL condition (/) > - Guided decision table simple action (/) > - Guided decision table BRL action (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4367) Tests in drools coverage are not really using the executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4367?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4367: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Tests in drools coverage are not really using the executable model > ------------------------------------------------------------------ > > Key: DROOLS-4367 > URL: https://issues.redhat.com/browse/DROOLS-4367 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Daniel Rosa > Priority: Minor > > Such as > https://github.com/kiegroup/drools/blob/ba9c79c4bfaf9cfc1ec2363bee3865c3d... > Even if the test itself is parametrized, in the body it calls directly buildAll therefore discarding the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5394) Coverage Report Improvements (CVS File)

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5394?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5394: ----------------------------------- Sprint: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Coverage Report Improvements (CVS File) > --------------------------------------- > > Key: DROOLS-5394 > URL: https://issues.redhat.com/browse/DROOLS-5394 > Project: Drools > Issue Type: Enhancement > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > > Proposed solution tohttps://issues.redhat.com/browse/RHPAM-2616, is to put the same data shown on Coverage Report inside the generated CSV Report file. > This means to add following data: > Overall Stats (Available rules, executed rules, coverage percentage); > Rules counters -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5502) DMN Generate Strongly Typed Output Set

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5502?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5502: ----------------------------------- Sprint: 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 28-30 (from Jul 6)) > DMN Generate Strongly Typed Output Set > -------------------------------------- > > Key: DROOLS-5502 > URL: https://issues.redhat.com/browse/DROOLS-5502 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > > Currently DMN output values are rapresented as a map. > > By levering the strongly typed functionality we can provide a strongly typed output that can be used in swagger to document the output of a REST endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5378) Alpha Node ordering

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5378?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5378: ----------------------------------- Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Alpha Node ordering > ------------------- > > Key: DROOLS-5378 > URL: https://issues.redhat.com/browse/DROOLS-5378 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Re-order Alpha Node based on some strategies: > - Expression usage count > - Other strategies : Chapter 9 "Ordering Conditions" in http://i.stanford.edu/pub/cstr/reports/cs/tr/86/1124/CS-TR-86-1124.pdf > It would contribute to maximise sharing and minimise the number of evaluations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5528) Drools buisness central ldap authentication

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5528?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5528: -------------------------------- Sprint: 2020 Week 28-30 (from Jul 6) > Drools buisness central ldap authentication > ------------------------------------------- > > Key: DROOLS-5528 > URL: https://issues.redhat.com/browse/DROOLS-5528 > Project: Drools > Issue Type: Feature Request > Reporter: prabhat kumar > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5528) Drools buisness central ldap authentication

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5528?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5528. --------------------------------- Resolution: Rejected > Drools buisness central ldap authentication > ------------------------------------------- > > Key: DROOLS-5528 > URL: https://issues.redhat.com/browse/DROOLS-5528 > Project: Drools > Issue Type: Feature Request > Reporter: prabhat kumar > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5528) Drools buisness central ldap authentication

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5528?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5528: ------------------------------------------- [~prabhat31k] Hi, I posted one idea about the issue in the related drools-setup forum thread (https://groups.google.com/forum/#!topic/drools-setup/3TO-GcDvRRk). JIRA is basically used for an identified bug or feature request. Please use a forum for trouble-shooting. Thank you for your understanding! > Drools buisness central ldap authentication > ------------------------------------------- > > Key: DROOLS-5528 > URL: https://issues.redhat.com/browse/DROOLS-5528 > Project: Drools > Issue Type: Feature Request > Reporter: prabhat kumar > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5534) MarshallingException occurs during REST request (JSON) unmarshalling in KIE server.

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5534?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5534: -------------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > MarshallingException occurs during REST request (JSON) unmarshalling in KIE server. > ----------------------------------------------------------------------------------- > > Key: DROOLS-5534 > URL: https://issues.redhat.com/browse/DROOLS-5534 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Attachments: full_error_messages.txt, reproducer_02699633_1.zip > > > A user's decision service deployed on KIE server receives REST commands from client, MarshallingException due to class loading failure occurs during JSON unmarshalling before the commands are processed. I attached a simplified reproducer reproducer_02699633_1.zip expressing the issue, and the error message is like below: > {noformat} > Caused by: com.fasterxml.jackson.databind.exc.InvalidTypeIdException: Could not resolve type id 'com.example.reproducer.common.params.ContactParam' as a subtype of [simple type, class com.example.reproducer.common.base.IRuleParam]: no such class found > at [Source: (String)"{ "lookup" : "ksession-rules", "commands" : [ { "insert" : { "object" : { "com.example.reproducer.common.base.Fact1": { "parameter" : { "@class" : "com.example.reproducer.common.params.ContactParam", "contactInfo" : 123456789 } } } } }, { "fire-all-rules" : "" } ]}"; line: 1, column: 185] (through reference chain: org.drools.core.command.runtime.BatchExecutionCommandImpl["commands"]->java.util.ArrayList[0]->org.drools.core.command.runtime.rule.InsertObjectCommand["object"]->com.example.reproducer.common.base.Fact1["parameter"]) > {noformat} > For full error messages, see full_error_messages.txt in Attachment. > The user's decision service (kjar) uses classes in another module jar as a library. ContactParam class which is a sub type of IRuleParam interface is in the kjar and IRuleParam interface is in the module jar. > Also, @JsonTypeInfo(use = Id.CLASS) annotation is given to IRuleParam like below in order for JSON implementation to recognize a given class to Fact1.parameter as a sub type of IRuleParam. > {code:java} > @JsonTypeInfo(use = Id.CLASS) > public interface IRuleParam { > } > {code} > Both classes contained in the module jar and classes in the kjar should be loaded. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020