January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1795) [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1795: ----------------------------------- Sprint: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column. > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1795 > URL: https://issues.jboss.org/browse/DROOLS-1795 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Final > Reporter: Mark Coble > Assignee: Mark Coble > Priority: Minor > Fix For: 7.0.0.Final > > Attachments: guvnor-3507.png > > > If a condition BRL column is added to a DT with bound variables that are used in an action column and that variable name is subsequently changed, the attached error message occurs when updating the action column with the new variable name. In the attached message the original variable name is 'app'. Hitting 'ok' returns you to the DT which has actually refactored the DT with the new variable name and validation is successful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1701: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > FEEL code generation and compilation > ------------------------------------ > > Key: DROOLS-1701 > URL: https://issues.jboss.org/browse/DROOLS-1701 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1825: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1609: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > Augment FEEL AST node at compilation with return type > ----------------------------------------------------- > > Key: DROOLS-1609 > URL: https://issues.jboss.org/browse/DROOLS-1609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1946) DMN Editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1946: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > DMN Editor > ---------- > > Key: DROOLS-1946 > URL: https://issues.jboss.org/browse/DROOLS-1946 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: UX > Fix For: 7.6.0.Final > > > Place holder for all DMN Editor related activities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2280) Test RuleUnitTest.testNamingConventionOnDrlFile() uses OS specific separator character

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2280: ------------------------------------- Summary: Test RuleUnitTest.testNamingConventionOnDrlFile() uses OS specific separator character Key: DROOLS-2280 URL: https://issues.jboss.org/browse/DROOLS-2280 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.5.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi Priority: Minor When running testNamingConventionOnDrlFile test on Windows, it fails on NPE, because the engine cannot find the rule unit "org/kie/test/MyRuleUnit" defined in the test, because it contains "/" separator character. I will provide a fix to the test. For resolving the rule unit class, the engine uses OS independent character correctly here [1]. [1] https://github.com/kiegroup/drools/blob/5fad04919f255933bdd34afdb8da10b94... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2279) Realign extension registers test to master using DMNProfile

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2279?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2279: ---------------------------------------- Fixed with https://github.com/kiegroup/drools/commit/7997f8505a391eaa35506361d47e80a... As a result of [DROOLS-2264] the original extension register configuration mechanism is no longer supported. In order to use extension registers, it is now required to configure them using a DMNProfile. Migration guide. Can reference commit [7997f850|https://github.com/kiegroup/drools/commit/7997f8505a391eaa355063...] for an example of migration. 1. Create a DMNProfile with the desired extension registers. Example [create DMNProfile|https://github.com/kiegroup/drools/commit/7997f8505a391eaa3550...] 2. replace old configuration of extension register (system property or kmodule entry) with the configuration of the new DMNProfile created from step1. Examples: [Replace system property|https://github.com/kiegroup/drools/commit/7997f8505a391eaa355063...], [replace kmodule entry|https://github.com/kiegroup/drools/commit/7997f8505a391eaa35506361d...] > Realign extension registers test to master using DMNProfile > ----------------------------------------------------------- > > Key: DROOLS-2279 > URL: https://issues.jboss.org/browse/DROOLS-2279 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > Following work on [DROOLS-2264] the DMN extension register mechanism is no longer supported. > In order to use extension registers, it is now required to configure them using a DMNProfile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9742) ClassLoader leak in JBoss Threads caused by MDBs

by Markus Dlugi (JIRA)

Markus Dlugi created WFLY-9742: ---------------------------------- Summary: ClassLoader leak in JBoss Threads caused by MDBs Key: WFLY-9742 URL: https://issues.jboss.org/browse/WFLY-9742 Project: WildFly Issue Type: Bug Affects Versions: 11.0.0.Final Reporter: Markus Dlugi Assignee: Jason Greene Attachments: default-threads-tccl.png, jboss-threads-tccl-example.zip There is a classloader leak in JBoss Threads which is most noticable when deploying MDBs. When a new MDB is created and a new thread for the MDB is started in the JCA thread pool ("default-threads - x"), the thread will be created using the context classloader of the MDB's deployment unit. This is because [MessageDrivenComponent.activate()|https://github.com/wildfly/wildfly/blob...] sets the context classloader of the ServerService thread in order to create the MDB, and this classloader will then also be used by the child thread. In the default configuration, the threads in the default thread pool will not be terminated and therefore the thread will keep the reference to the classloader even when the deployment unit is undeployed. This in turn can lead to "OutOfMemoryError: Metaspace" after a couple of redeployments. As a workaround, we changed [JBossThreadFactory.createThread()|https://github.com/jbossas/jboss-thread...] to set the context classloader to null after a new thread has been created. While this fixes the issue for us, I am not sure whether this is a good solution for all consumers of the thread factory, or if this should be fixed in the JCA subsystem instead. That's also the reason why I opened this issue against the WildFly project instead of JBoss Threads. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1505) org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1505?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1505: ------------------------------- Assignee: Jan Kalina (was: Ivo Studensky) > org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161 > ---------------------------------------------------------------- > > Key: ELY-1505 > URL: https://issues.jboss.org/browse/ELY-1505 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Reporter: Ivo Studensky > Assignee: Jan Kalina > Priority: Minor > > The org.wildfly.security.asn1.DEREncoderTest#testEncodeDSAKey() fails on JDK8 v.161 due to: > {noformat} > [ERROR] testEncodeDSAKey(org.wildfly.security.asn1.DEREncoderTest) Time elapsed: 0.124 s <<< ERROR! > java.security.InvalidKeyException: The security strength of SHA-1 digest algorithm is not sufficient for this key size > at sun.security.provider.DSA.checkKey(DSA.java:111) > at sun.security.provider.DSA.engineInitSign(DSA.java:143) > at java.security.Signature$Delegate.init(Signature.java:1156) > at java.security.Signature$Delegate.chooseProvider(Signature.java:1116) > at java.security.Signature$Delegate.engineInitSign(Signature.java:1180) > at java.security.Signature.initSign(Signature.java:531) > at org.wildfly.security.asn1.DEREncoderTest.testEncodeDSAKey(DEREncoderTest.java:458) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {noformat} > It affects also older tags, not only 1.1.8. It might be related to > https://bugs.java.com/view_bug.do?bug_id=8184341 > It seems to be a testsuite issue only. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2233) DMN: time(date("2017-08-10")) should return 00:00:00z time

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2233?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-2233: --------------------------------------- Merged as part of this PR https://github.com/kiegroup/drools/pull/1711 > DMN: time(date("2017-08-10")) should return 00:00:00z time > ---------------------------------------------------------- > > Key: DROOLS-2233 > URL: https://issues.jboss.org/browse/DROOLS-2233 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.5.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > Fix For: 7.6.0.Final > > > According to the specification in section "10.3.2.3.5 date": > "Where necessary, including the valuedt function (see 10.3.2.x.6), a date value is considered to be equivalent to a date time value in which the time of day is UTC midnight (00:00:00)." > Currently the case time(date("2017-08-10")) returns null, because the evaluation ends with DateTimeException, because internally we represent dates as LocalDate class, which doesn't have time part. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018