May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5349) Guided Decision Table Attribute Column default value not working

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5349?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5349: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4)) > Guided Decision Table Attribute Column default value not working > ------------------------------------------------------------------ > > Key: DROOLS-5349 > URL: https://issues.redhat.com/browse/DROOLS-5349 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.38.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: guided_decision_table > Attachments: GuidedDecisionTable-Attribute-boolean-switch-notworking.gif, Screenshot from 2020-05-15 16-24-29.png > > > When adding an Attribute Column (eg: no-loop) and changing it's default value (from true to false or vice-versa) this change is not reflected on the table model nor in the source. > Please see the gif recording attached. > It can be non intuitive for newcomers. We should mention that changing column default value will affect just new added rows. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5352) Wrong navigation after spreadsheet decision table creation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5352?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5352: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4)) > Wrong navigation after spreadsheet decision table creation > ---------------------------------------------------------- > > Key: DROOLS-5352 > URL: https://issues.redhat.com/browse/DROOLS-5352 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.38.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > Attachments: current-behavior.webm, expected-behavior.webm > > > The issue can be spotted when new decison table spreadsheet is created in business central. The proiblem is instead of showing xls/xlsx editor automatically when upload finishes we show some 'Other' file type editor. > Compare the attached videos. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5353) Avoid ClassLoader retention in LambdaIntrospector

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5353?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5353: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4)) > Avoid ClassLoader retention in LambdaIntrospector > ------------------------------------------------- > > Key: DROOLS-5353 > URL: https://issues.redhat.com/browse/DROOLS-5353 > Project: Drools > Issue Type: Enhancement > Components: executable model > Affects Versions: 7.37.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Change LambdaIntrospector$ClassIdentifier not to retain ClassLoader itself so that we no longer need to worry about ClassLoader leak. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5327: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4)) > Multiselect dropdown for enumerated values - numbers > ---------------------------------------------------- > > Key: DROOLS-5327 > URL: https://issues.redhat.com/browse/DROOLS-5327 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > Attachments: MySpace_project.zip > > > During verification of DROOLS-5011 was spotted corner case that was not fixed. > In the original issue customer user attached project with enumeration for *String* field and used that field in guided rule template. > The issue is if user follow the same scenario but instead of *String* field, some number type is used, for example *Integer*. In such case, when user added data to rule template, multiselect dropdown was shown correctly, however in the grid was always shown 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5329) Review externalizing lambda failure case

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5329?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5329: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4)) > Review externalizing lambda failure case > ---------------------------------------- > > Key: DROOLS-5329 > URL: https://issues.redhat.com/browse/DROOLS-5329 > Project: Drools > Issue Type: Task > Components: executable model > Affects Versions: 7.37.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > In CompilerTest#testStringValueOf, there is a case where MaterializedLambdaPredicate is not created. > {code:java} > public static org.drools.model.Rule rule_R() { > final org.drools.model.Variable<java.lang.Integer> var_GENERATED_$pattern_Integer$1$ = D.declarationOf(java.lang.Integer.class, > DomainClassesMetadata81A66AD685F7689036AAA5128956C14B.java_lang_Integer_Metadata_INSTANCE, > "GENERATED_$pattern_Integer$1$"); > final org.drools.model.Variable<Integer> var_$i = D.declarationOf(Integer.class, "$i"); > final org.drools.model.Variable<org.drools.modelcompiler.domain.Person> var_GENERATED_$pattern_Person$1$ = D.declarationOf(org.drools.modelcompiler.domain.Person.class, > DomainClassesMetadata81A66AD685F7689036AAA5128956C14B.org_drools_modelcompiler_domain_Person_Metadata_INSTANCE, > "GENERATED_$pattern_Person$1$"); > org.drools.model.Rule rule = D.rule("R").build(D.pattern(var_GENERATED_$pattern_Integer$1$).bind(var_$i, (java.lang.Integer _this) -> _this.intValue()), > D.pattern(var_GENERATED_$pattern_Person$1$).expr("476633DA7C4638FC84A32859E0C843E6", > var_$i, > (_this, $i) -> org.drools.modelcompiler.util.EvaluationUtil.areNullSafeEquals(_this.getName(), > (String.valueOf($i))), > D.reactOn("name")), > D.on(var_$i).execute(defaultpkg.P1D.LambdaConsequence1D5F4C5CA006007B1D3974ED5A5A05B6.INSTANCE)); > return rule; > } > {code} > See > {code:java} > expr("476633DA7C4638FC84A32859E0C843E6", > var_$i, > (_this, $i) -> org.drools.modelcompiler.util.EvaluationUtil.areNullSafeEquals(_this.getName(), > (String.valueOf($i))) > {code} > It throws DoNotConvertLambdaException in ExecModelLambdaPostProcessor. > {code:java} > private void extractLambdaFromMethodCall(MethodCallExpr methodCallExpr, Supplier<MaterializedLambda> lambdaExtractor) { > methodCallExpr.getArguments().forEach(a -> { > if (a.isLambdaExpr()) { > LambdaExpr lambdaExpr = a.asLambdaExpr(); > try { > CreatedClass aClass = lambdaExtractor.get().create(lambdaExpr.toString(), imports, staticImports); > lambdaClasses.put(aClass.getClassNameWithPackage(), aClass); > ClassOrInterfaceType type = StaticJavaParser.parseClassOrInterfaceType(aClass.getClassNameWithPackage()); > a.replace(lambdaInstance(type)); > } catch(DoNotConvertLambdaException e) { > logger.debug("Cannot externalize lambdas {}", e.getMessage()); > } > } > }); > } > {code} > Review if it's something can be fixed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5333: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4)) > Allow to customize rule names in guided decision table editor > ------------------------------------------------------------- > > Key: DROOLS-5333 > URL: https://issues.redhat.com/browse/DROOLS-5333 > Project: Drools > Issue Type: Feature Request > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Add a column into the GDST where you can set the rule name for the rule that is generated from that row. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[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) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4)) > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5284) MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5284?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5284: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4)) > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > ---------------------------------------------------------- > > Key: DROOLS-5284 > URL: https://issues.redhat.com/browse/DROOLS-5284 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.36.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > {noformat} > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.97 s <<< FAILURE! - in org.drools.compiler.integrationtests.MVELTest > [ERROR] testTypeCoercionLongDivByInt(org.drools.compiler.integrationtests.MVELTest) Time elapsed: 0.962 s <<< FAILURE! > java.lang.AssertionError: expected:<7.350000> but was:<7> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.drools.compiler.integrationtests.MVELTest.testTypeCoercionLongDivByInt(MVELTest.java:1150) > ... > [INFO] > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] MVELTest.testTypeCoercionLongDivByInt:1150 expected:<7.350000> but was:<7> > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4)) > 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)

6 years, 1 month

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) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4)) > 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)

6 years, 1 month

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 May 2020