July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5484) DMN test DT in context reports warn of no matched rules

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5484?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5484: ----------------------------------- Description: follows up on https://github.com/kiegroup/drools/commit/01e8ff9d9a38e3232d532c879b24a8a... and https://github.com/kiegroup/drools/commit/49be6c816880f64262eb0cdb08bcb59... to make sure the WARN of no matched rules also applies when the DT is in context (entries and result) > DMN test DT in context reports warn of no matched rules > ------------------------------------------------------- > > Key: DROOLS-5484 > URL: https://issues.redhat.com/browse/DROOLS-5484 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > follows up on > https://github.com/kiegroup/drools/commit/01e8ff9d9a38e3232d532c879b24a8a... > and > https://github.com/kiegroup/drools/commit/49be6c816880f64262eb0cdb08bcb59... > to make sure the WARN of no matched rules also applies when the DT is in context (entries and result) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5484) DMN test DT in context reports warn of no matched rules

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5484: -------------------------------------- Summary: DMN test DT in context reports warn of no matched rules Key: DROOLS-5484 URL: https://issues.redhat.com/browse/DROOLS-5484 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5483) RulesByteArray is never persistent into SessionInfo Table

by Agustino Alim (Jira)

Agustino Alim created DROOLS-5483: ------------------------------------- Summary: RulesByteArray is never persistent into SessionInfo Table Key: DROOLS-5483 URL: https://issues.redhat.com/browse/DROOLS-5483 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.39.0.Final Reporter: Agustino Alim Assignee: Mario Fusco Hello, When I deploy KIE Application into Karaf which doesn't support build-in capability of TransactionSynchronizationRegistry, so it will fallback into implementation with ThreadLocal [https://github.com/kiegroup/drools/blob/master/drools-persistence/drools-...] What's happening is during commit, the transaction resource is always clear no matter the caller own the transaction or not. {code:java} public void commit(boolean transactionOwner) { if ( transactionOwner ) { try { this.ut.commit(); } catch ( Exception e ) { logger.warn( "Unable to commit transaction", e); throw new RuntimeException( "Unable to commit transaction", e ); } } transactionResources.get().clear(); } {code} This causes rulesbytearray field in sessioninfo table is not persisted. Please refer to comment from ngs-mtech on [JtaTransactionManager.java|https://github.com/kiegroup/drools/commit/... [https://github.com/kiegroup/drools/commit/6189bdfaed78d540b464b83bcf6de5b...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5482) Extending integration tests to cover transformations

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5482: ---------------------------------------- Summary: Extending integration tests to cover transformations Key: DROOLS-5482 URL: https://issues.redhat.com/browse/DROOLS-5482 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Extend integration tests to cover tranformations implementation (Apply/FieldRef/Constant) - eventually fixing bug -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5473) Implement DefineFunction scheleton

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5473?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5473. ------------------------------------ > Implement DefineFunction scheleton > ---------------------------------- > > Key: DROOLS-5473 > URL: https://issues.redhat.com/browse/DROOLS-5473 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Implement DefineFunction management scheleton. > DefineFunctions are similar to DerivedFields, since both make usage of EXPRESSION. > Differences are > 1) DerivedFields methods should referenced inside "transformations" map, DefineFunctions not > 2) DerivedFields methods names are automatically generated, while DefineFunctions ones are retrieved from DefinedFunctions declaration > 3) DefineFunctions requires at least one Parameter (beside the List of already defined fields ) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13642) Legacy store=remote throws NCDFE at runtime

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13642?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13642: -------------------------------- Priority: Major (was: Blocker) > Legacy store=remote throws NCDFE at runtime > ------------------------------------------- > > Key: WFLY-13642 > URL: https://issues.redhat.com/browse/WFLY-13642 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 20.0.1.Final > > > The remote-store references a marshaller from the infinispan jboss-marshalling module, which WF does not include, thus throws a NoClassDefFoundError at runtime if one is configured. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13642) Legacy store=remote throws NCDFE at runtime

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13642?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13642: -------------------------------- Workaround Description: If the remote-store is not configured with rawtypes enabled, then it *should* use the persistence marshaller, and not try to instantiate its own JBoss Marshaller. Workaround: Workaround Exists > Legacy store=remote throws NCDFE at runtime > ------------------------------------------- > > Key: WFLY-13642 > URL: https://issues.redhat.com/browse/WFLY-13642 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 20.0.1.Final > > > The remote-store references a marshaller from the infinispan jboss-marshalling module, which WF does not include, thus throws a NoClassDefFoundError at runtime if one is configured. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5031) Remove the audit-log deprecation

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFCORE-5031?page=com.atlassian.jira.plug... ] Ranabir Chakraborty updated WFCORE-5031: ---------------------------------------- Summary: Remove the audit-log deprecation (was: [GSS](7.3.z) remove the audit-log deprecation) > Remove the audit-log deprecation > -------------------------------- > > Key: WFCORE-5031 > URL: https://issues.redhat.com/browse/WFCORE-5031 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Ranabir Chakraborty > Assignee: Ranabir Chakraborty > Priority: Minor > > Remove the audit-log deprecation as it was deprecated when planning to move the core-management=xxx resources into subsystems, but focus has since shifted from management to making our stuff work better in images. > *Deprecated* Since 1.7.0 > The management audit log configuration is deprecated and may be removed or moved in future versions. > [http://wildscribe.github.io/JBoss%20EAP/7.2/core-service/management/acces...] > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5478) Propagate Returned type info to avoid "Object" returned types

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5478?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5478: ------------------------------------- Summary: Propagate Returned type info to avoid "Object" returned types (was: Propagate DataDictionary to avoid "Object" returned types) > Propagate Returned type info to avoid "Object" returned types > ------------------------------------------------------------- > > Key: DROOLS-5478 > URL: https://issues.redhat.com/browse/DROOLS-5478 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > FieldRef and Apply functions does not define directly the returned type. > Propagating DataDictionary will allow to avoid generic "Object" return and replace it with specific one -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5478) Propagate Returned type info to avoid "Object" returned types

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5478?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5478: ------------------------------------- Description: FieldRef and Apply functions does not define directly the returned type. Propagating the expected returned type will allow to avoid generic "Object" return and replace it with specific one was: FieldRef and Apply functions does not define directly the returned type. Propagating DataDictionary will allow to avoid generic "Object" return and replace it with specific one > Propagate Returned type info to avoid "Object" returned types > ------------------------------------------------------------- > > Key: DROOLS-5478 > URL: https://issues.redhat.com/browse/DROOLS-5478 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > FieldRef and Apply functions does not define directly the returned type. > Propagating the expected returned type will allow to avoid generic "Object" return and replace it with specific one -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

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