October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1751) NullPointerException on org.mvel2.MVEL.executeExpression()

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1751?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1751: -------------------------------- Sprint: 2017 Week 40-41 > NullPointerException on org.mvel2.MVEL.executeExpression() > ---------------------------------------------------------- > > Key: DROOLS-1751 > URL: https://issues.jboss.org/browse/DROOLS-1751 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.3.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Labels: support > > Under the conditions: > - 2 KiePackages with the same package name but different rules > - Those packages are used by a kbase so "inUse = true" > - Create another kbase and call kbase.addPackages() for those packages > MVELDialectRuntimeData has a problem in merging mvelReaders so later rule execution fails with NullPointerException. > {noformat} > java.lang.NullPointerException: null > at org.mvel2.MVEL.executeExpression(MVEL.java:953) > at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:506) > at org.drools.core.base.extractors.MVELObjectClassFieldReader.getValue(MVELObjectClassFieldReader.java:140) > at org.drools.core.rule.Declaration.getValue(Declaration.java:222) > at org.drools.core.base.mvel.MVELCompilationUnit.updateFactory(MVELCompilationUnit.java:386) > at org.drools.core.base.mvel.MVELCompilationUnit.getFactory(MVELCompilationUnit.java:320) > at org.drools.core.base.dataproviders.MVELDataProvider.evaluate(MVELDataProvider.java:137) > at org.drools.core.base.dataproviders.MVELDataProvider.getResults(MVELDataProvider.java:133) > at org.drools.core.phreak.PhreakFromNode.doLeftInserts(PhreakFromNode.java:106) > at org.drools.core.phreak.PhreakFromNode.doNode(PhreakFromNode.java:68) > at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:387) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87) > at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34) > at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067) > at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1320) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1311) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1295) > at org.drools.compiler.integrationtests.Misc2Test.testMergeMVELDialect(Misc2Test.java:9109) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1388) Clean up credential-store-type in schema

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1388: ------------------------------------- Summary: Clean up credential-store-type in schema Key: ELY-1388 URL: https://issues.jboss.org/browse/ELY-1388 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Affects Versions: 1.2.0.Beta4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 The credential store type contains the following definition: - {code} <xsd:complexType name="credential-store-type"> <xsd:annotation> <xsd:documentation> An individual credential store definition. </xsd:documentation> </xsd:annotation> <xsd:all minOccurs="0" maxOccurs="1"> <xsd:element name="attributes" type="attributes-type"/> <xsd:element name="protection-parameter-credentials" type="client-credentials-type"/> <xsd:element name="providers" type="providers-type" /> </xsd:all> <xsd:attribute name="name" type="xsd:string" use="required" /> <xsd:attribute name="type" type="xsd:string" default="KeyStoreCredentialStore" use="optional"> <xsd:annotation> <xsd:documentation> The credential store type, e.g. KeyStoreCredentialStore. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="provider" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> The name of the provider to use to instantiate the CredentialStoreSpi, if the provider is not specified then the first provider found that can create an instance of the specified 'type' will be used. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:complexType> {code} This effectively says the child elements are optional but if one is specified they all need to be specified, however they are all optional and can be specified individually. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1387) SSLContext for where authentication client resources load from a resource.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1387: ------------------------------------- Summary: SSLContext for where authentication client resources load from a resource. Key: ELY-1387 URL: https://issues.jboss.org/browse/ELY-1387 Project: WildFly Elytron Issue Type: Enhancement Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 Where resources can be loaded from a URI we may want to define an SSLContext for access to that resource so we can verify it is a trusted resource. i.e. our local config contains internal key and trust stores but the remove destinations may change so we load the certificates and revocation lists from an internal trusted source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1386) <certificate-revocation-list /> should also support a URI and resource in addition to path.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1386: ------------------------------------- Summary: <certificate-revocation-list /> should also support a URI and resource in addition to path. Key: ELY-1386 URL: https://issues.jboss.org/browse/ELY-1386 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 KeyStores can be loaded from a path, a URI, or as a resource - the certificate revocation list should be the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1385) Add option to override the KeyManager and TrustManager within <authentication-client />

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1385: ------------------------------------- Summary: Add option to override the KeyManager and TrustManager within <authentication-client /> Key: ELY-1385 URL: https://issues.jboss.org/browse/ELY-1385 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 At the moment we can reference an alias from a KeyStore and reference a complete KeyStore for use by the TrustManager but there is not option to override which key and trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7304) Compensations subsystem

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-7304?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned WFLY-7304: ------------------------------------- Assignee: Ondra Chaloupka (was: Gytis Trikleris) > Compensations subsystem > ----------------------- > > Key: WFLY-7304 > URL: https://issues.jboss.org/browse/WFLY-7304 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 11.0.0.Final > > > Currently compensations bootstrap happens in the transactions subsystem. It registers deployment processor to scan the annotations and add the dependencies if necessary. This is not expensive and doesn't cause any issues other than adding the dependencies to the transactions subsystem. However, I'm currently finishing off the recovery implementation and more bootstrap logic will be needed. In addition, two more recovery modules will have to be registered: one for the participant (a new one) and one for the coordinator (from XTS). This will require to add XTS dependency too. > The whole compensations bootstrapping will not need a lot of code. However, I'm thinking maybe it would be good to pull it out to the separate subsystem in order to maintain the separation of concerns. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1678) Unary test "in" defined before variable throws NPE

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1678?page=com.atlassian.jira.plugi... ] Fedor Gavrilov reassigned DROOLS-1678: -------------------------------------- Assignee: Fedor Gavrilov (was: Edson Tirelli) > Unary test "in" defined before variable throws NPE > -------------------------------------------------- > > Key: DROOLS-1678 > URL: https://issues.jboss.org/browse/DROOLS-1678 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Fedor Gavrilov > Fix For: 7.4.0.Final > > > Having this DMN test with Unary test defined: > {code:java} > { test : in x, y : 20, x : [10, 20, 30], result : test( y ) }.result > {code} > The test fails on NPE with the following stacktrace: > https://gist.github.com/baldimir/630c68e766285e430a1755924ea9a66b -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9421) Update testsuite to use EAP70 enum values and not just api versions

by Kabir Khan (JIRA)

Kabir Khan created WFLY-9421: -------------------------------- Summary: Update testsuite to use EAP70 enum values and not just api versions Key: WFLY-9421 URL: https://issues.jboss.org/browse/WFLY-9421 Project: WildFly Issue Type: Bug Components: Domain Management, Test Suite Affects Versions: 11.0.0.CR1 Reporter: Ken Wills Assignee: Ken Wills Priority: Blocker Fix For: 11.0.0.Final The associated issue in wildfly-core is: WFCORE-3226 The existing tests in mixed-domain should be updated to use this enum value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1746) API changes review for Drools Core

by Andrey V. Ponomarenko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1746?page=com.atlassian.jira.plugi... ] Andrey V. Ponomarenko commented on DROOLS-1746: ----------------------------------------------- Report for KIE Public API: https://abi-laboratory.pro/java/tracker/timeline/kie-api/ Please let me know if you'd like to add more libraries to the tracker. Thank you. !kie-api-2.png|thumbnail! !kie-api-1.png|thumbnail! > API changes review for Drools Core > ---------------------------------- > > Key: DROOLS-1746 > URL: https://issues.jboss.org/browse/DROOLS-1746 > Project: Drools > Issue Type: Enhancement > Reporter: Andrey V. Ponomarenko > Assignee: Edson Tirelli > Attachments: drools-core-1.png, drools-core-2.png, kie-api-1.png, kie-api-2.png > > > The review of API changes for the Drools Core library since 6.3.0 version: https://abi-laboratory.pro/java/tracker/timeline/drools-core/ > Hope it will be helpful for users and maintainers of the library. > The report is generated by the https://github.com/lvc/japi-tracker tool for jars found at http://central.maven.org/maven2/org/drools/drools-core/ according to https://wiki.eclipse.org/Evolving_Java-based_APIs_2. > Thank you. > !drools-core-2.png|API symbols timeline! > !drools-core-1.png|API changes review! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1746) API changes review for Drools Core

by Andrey V. Ponomarenko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1746?page=com.atlassian.jira.plugi... ] Andrey V. Ponomarenko updated DROOLS-1746: ------------------------------------------ Attachment: kie-api-1.png > API changes review for Drools Core > ---------------------------------- > > Key: DROOLS-1746 > URL: https://issues.jboss.org/browse/DROOLS-1746 > Project: Drools > Issue Type: Enhancement > Reporter: Andrey V. Ponomarenko > Assignee: Edson Tirelli > Attachments: drools-core-1.png, drools-core-2.png, kie-api-1.png, kie-api-2.png > > > The review of API changes for the Drools Core library since 6.3.0 version: https://abi-laboratory.pro/java/tracker/timeline/drools-core/ > Hope it will be helpful for users and maintainers of the library. > The report is generated by the https://github.com/lvc/japi-tracker tool for jars found at http://central.maven.org/maven2/org/drools/drools-core/ according to https://wiki.eclipse.org/Evolving_Java-based_APIs_2. > Thank you. > !drools-core-2.png|API symbols timeline! > !drools-core-1.png|API changes review! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 October 2017