June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1613) NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1613?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1613: ---------------------------------- Sprint: 2017 Week 24-25 > NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1613 > URL: https://issues.jboss.org/browse/DROOLS-1613 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Fix For: 7.1.0.Final > > > When I have a decision table with hit policy Priority and multiple outputs and I change one of the outputs in a rule to a wrong type, the evaluation ends with NullPointerException. > E.g. having output entry like this: > <outputEntry id="_7f03803d-2636-40ab-8346-7fd7f38ab695-3"> > <text>1</text> > </outputEntry> > I will provide PR with reproducer for this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1597) Implement profile for integration with Signavio's DMN modeler

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1597?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1597: ---------------------------------- Sprint: 2017 Week 24-25 > Implement profile for integration with Signavio's DMN modeler > ------------------------------------------------------------- > > Key: DROOLS-1597 > URL: https://issues.jboss.org/browse/DROOLS-1597 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > > Signavio implements a number of extensions to the DMN standard. As they are a Red Hat partner, we will need to implement a profile in the runtime engine that enables and supports those extensions. > A short list of extensions is as follows. Details will be added to individual tickets: > * Support additional FEEL functions and alternate names for existing functions > * Support the Multi Instance Decision node > * Support character '?' for interpolation of values in a DT cell > * Support constraints on List inputs in DT cells > * Support model composition through BKMs -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1612) Throw compilation error when using collect hit policy with aggr. function and multiple outputs

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1612?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1612: ---------------------------------- Sprint: 2017 Week 24-25 > Throw compilation error when using collect hit policy with aggr. function and multiple outputs > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-1612 > URL: https://issues.jboss.org/browse/DROOLS-1612 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > > According to the DMN spec., "Decision tables with compound outputs support only the following hit policies: Unique, Any, Priority, First, Output > order, Rule order and Collect without operator, because the collect operator is undefined over multiple outputs." > However when I use decision table with "COLLECT" hit policy, "sum" aggregate function and multiple outputs, the table compiles. When evaluating the table, I get nulls as output value results, but no error message in DMNResult. > I will provide a reproducer in a PR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2944) Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2944?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-2944 at 6/12/17 10:13 AM: -------------------------------------------------------------------- I don't think it's likely we'll change this as doing it would be probably be quite invasive and bug prone. The issue is a particular deployment resource is persistent or not due to the value of a special attribute in that resource. The kernel, which decides whether the model has been modified, knows nothing about this special value, only the xml marshaller of the resource does. It's not a general concept of the model; it's kind of a specialized hack for one resource type. was (Author: brian.stansberry): I think there was another issue about this, or perhaps an internal support list discussion. I don't think it's likely we'll change this as doing it would be probably be quite invasive and bug prone. The issue is a particular deployment resource is persistent or not due to the value of a special attribute in that resource. The kernel, which decides whether the model has been modified, knows nothing about this special value, only the xml marshaller of the resource does. It's not a general concept of the model; it's kind of a specialized hack for one resource type. > Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-2944 > URL: https://issues.jboss.org/browse/WFCORE-2944 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Wolf-Dieter Fink > Priority: Minor > > It is not expected that the standalone.xml is written and versions or other content is updated. > e.g. the top level element > <server xmlns="urn:jboss:domain:x.y"> > It is expected that the standalone configuration is updated with the latest namespace versions, or other changes, if the configuration needs to be persisted. > But for any unmanged deployment it is not expected and not necessary to update the configuration file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1584) Null pointer Exception while Scanner trying to pull updates from Kie Workbench

by Dhamodharan Krishnan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1584?page=com.atlassian.jira.plugi... ] Dhamodharan Krishnan commented on DROOLS-1584: ---------------------------------------------- [~mfusco] This issue with the server within our client network. I will setup a personal instance on my personal laptop and try to reproduce the error logs. As I cannot get the logs from the client network. > Null pointer Exception while Scanner trying to pull updates from Kie Workbench > ------------------------------------------------------------------------------ > > Key: DROOLS-1584 > URL: https://issues.jboss.org/browse/DROOLS-1584 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.5.0.Final > Environment: Mac. > Reporter: Dhamodharan Krishnan > Assignee: Mario Fusco > > May 25, 2017 10:07:34 PM org.drools.compiler.kie.builder.impl.KieRepositoryImpl addKieModule > INFO: KieModule was added: ZipKieModule[releaseId=com.mycompany.module:project:2.0-SNAPSHOT,file=/Users/dhamo/.m2/repository/com/mycompany/module/project/2.0-SNAPSHOT/project-2.0-SNAPSHOT.jar] > Exception in thread "Timer-0" java.lang.NullPointerException > at org.drools.core.reteoo.BetaMemory.linkNode(BetaMemory.java:93) > at org.drools.core.reteoo.BetaMemory.linkNode(BetaMemory.java:88) > at org.drools.core.reteoo.SingleObjectSinkAdapter.staticDoLinkRiaNode(SingleObjectSinkAdapter.java:104) > at org.drools.core.reteoo.SingleObjectSinkAdapter.doLinkRiaNode(SingleObjectSinkAdapter.java:86) > at org.drools.core.reteoo.RiaPathMemory.doLinkRule(RiaPathMemory.java:50) > at org.drools.core.reteoo.PathMemory.linkSegment(PathMemory.java:102) > at org.drools.core.reteoo.SegmentMemory.notifyRuleLinkSegment(SegmentMemory.java:192) > at org.drools.core.phreak.AddRemoveRule.addNewPaths(AddRemoveRule.java:459) > at org.drools.core.phreak.AddRemoveRule.addRule(AddRemoveRule.java:126) > at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:190) > at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:133) > at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:106) > at org.drools.core.impl.KnowledgeBaseImpl.addRule(KnowledgeBaseImpl.java:1586) > at org.drools.core.impl.KnowledgeBaseImpl.addRule(KnowledgeBaseImpl.java:1566) > at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileAllRules(KnowledgeBuilderImpl.java:1004) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildRules(CompositeKnowledgeBuilderImpl.java:264) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:122) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:105) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.rebuildAll(KieContainerImpl.java:449) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.updateKBase(KieContainerImpl.java:311) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.access$000(KieContainerImpl.java:88) > at org.drools.compiler.kie.builder.impl.KieContainerImpl$1.run(KieContainerImpl.java:255) > at org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:735) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:252) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.updateDependencyToVersion(KieContainerImpl.java:218) > at org.kie.scanner.KieRepositoryScannerImpl.updateKieModule(KieRepositoryScannerImpl.java:317) > at org.kie.scanner.KieRepositoryScannerImpl.scanNow(KieRepositoryScannerImpl.java:298) > at org.kie.scanner.KieRepositoryScannerImpl$ScanTask.run(KieRepositoryScannerImpl.java:270) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8915) Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8915?page=com.atlassian.jira.plugin.... ] Brian Stansberry edited comment on WFLY-8915 at 6/12/17 10:08 AM: ------------------------------------------------------------------ I think there was another issue about this, or perhaps an internal support list discussion. I don't think it's likely we'll change this as doing it would be probably be quite invasive and bug prone. The issue is a particular deployment resource is persistent or not due to the value of a special attribute in that resource. The kernel, which decides whether the model has been modified, knows nothing about this special value, only the xml marshaller of the resource does. It's not a general concept of the model; it's kind of a specialized hack for one resource type. was (Author: brian.stansberry): I think there was another issue about this, or perhaps an internal support list discussion. I don't think it's likely we'll change this as doing it would be probably be quite invasive and bug prone. > Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-8915 > URL: https://issues.jboss.org/browse/WFLY-8915 > Project: WildFly > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > Priority: Minor > > It is not expected that the standalone.xml is written and versions or other content is updated. > e.g. the top level element > <server xmlns="urn:jboss:domain:x.y"> > It is expected that the standalone configuration is updated with the latest namespace versions, or other changes, if the configuration needs to be persisted. > But for any unmanged deployment it is not expected and not necessary to update the configuration file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2944) Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2944?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8915 to WFCORE-2944: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2944 (was: WFLY-8915) Affects Version/s: (was: 11.0.0.Alpha1) > Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-2944 > URL: https://issues.jboss.org/browse/WFCORE-2944 > Project: WildFly Core > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > Priority: Minor > > It is not expected that the standalone.xml is written and versions or other content is updated. > e.g. the top level element > <server xmlns="urn:jboss:domain:x.y"> > It is expected that the standalone configuration is updated with the latest namespace versions, or other changes, if the configuration needs to be persisted. > But for any unmanged deployment it is not expected and not necessary to update the configuration file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2136) Using management CLI with client configuration still prompts for username/password

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2136?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2136: ------------------------------- Fix Version/s: 3.0.0.Beta22 (was: 3.0.0.Beta27) > Using management CLI with client configuration still prompts for username/password > ---------------------------------------------------------------------------------- > > Key: WFCORE-2136 > URL: https://issues.jboss.org/browse/WFCORE-2136 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Security > Reporter: Zach Rhoads > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta22 > > > When configuring the wildfly management cli to use an elytron client config file, server still prompts for username password. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2136) Using management CLI with client configuration still prompts for username/password

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2136?page=com.atlassian.jira.plugi... ] Kabir Khan resolved WFCORE-2136. -------------------------------- Resolution: Done > Using management CLI with client configuration still prompts for username/password > ---------------------------------------------------------------------------------- > > Key: WFCORE-2136 > URL: https://issues.jboss.org/browse/WFCORE-2136 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Security > Reporter: Zach Rhoads > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta22 > > > When configuring the wildfly management cli to use an elytron client config file, server still prompts for username password. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1613) NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1613?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-1613: -------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1613 > URL: https://issues.jboss.org/browse/DROOLS-1613 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Fix For: 7.1.0.Final > > > When I have a decision table with hit policy Priority and multiple outputs and I change one of the outputs in a rule to a wrong type, the evaluation ends with NullPointerException. > E.g. having output entry like this: > <outputEntry id="_7f03803d-2636-40ab-8346-7fd7f38ab695-3"> > <text>1</text> > </outputEntry> > I will provide PR with reproducer for this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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