March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2420) [DMN Designer] Hit Policy Collect does not need an Aggregation function

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2420?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2420: -------------------------------- Description: Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" h2. Acceptance test # After saving and reopening is user able to achieve Collect hit policy ## with aggregating function ## without aggregating function # After saving and reopening is user able to change ## From any collect hit policy to non collect hit policy ## From non collect hit policy to collect hit policy # Change of hit policy is reflected in dmn file was: Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" .h2 Acceptance test # After saving and reopening is user able to achieve Collect hit policy ## with aggregating function ## without aggregating function # After saving and reopening is user able to change ## From any collect hit policy to non collect hit policy ## From non collect hit policy to collect hit policy # Change of hit policy is reflected in dmn file > [DMN Designer] Hit Policy Collect does not need an Aggregation function > ----------------------------------------------------------------------- > > Key: DROOLS-2420 > URL: https://issues.jboss.org/browse/DROOLS-2420 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" > h2. Acceptance test > # After saving and reopening is user able to achieve Collect hit policy > ## with aggregating function > ## without aggregating function > # After saving and reopening is user able to change > ## From any collect hit policy to non collect hit policy > ## From non collect hit policy to collect hit policy > # Change of hit policy is reflected in dmn file -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2420) [DMN Designer] Hit Policy Collect does not need an Aggregation function

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2420?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2420: -------------------------------- Description: Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" .h2 Acceptance test # After saving and reopening is user able to achieve Collect hit policy ## with aggregating function ## without aggregating function # After saving and reopening is user able to change ## From any collect hit policy to non collect hit policy ## From non collect hit policy to collect hit policy # Change of hit policy is reflected in dmn file was:Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" > [DMN Designer] Hit Policy Collect does not need an Aggregation function > ----------------------------------------------------------------------- > > Key: DROOLS-2420 > URL: https://issues.jboss.org/browse/DROOLS-2420 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" > .h2 Acceptance test > # After saving and reopening is user able to achieve Collect hit policy > ## with aggregating function > ## without aggregating function > # After saving and reopening is user able to change > ## From any collect hit policy to non collect hit policy > ## From non collect hit policy to collect hit policy > # Change of hit policy is reflected in dmn file -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2420) [DMN Designer] Hit Policy Collect does not need an Aggregation function

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2420?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2420: -------------------------------- Tester: Jozef Marko > [DMN Designer] Hit Policy Collect does not need an Aggregation function > ----------------------------------------------------------------------- > > Key: DROOLS-2420 > URL: https://issues.jboss.org/browse/DROOLS-2420 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2421) Unexpected response from rule engine for windowing rules

by Bishnu Shankar Pandey (JIRA)

Bishnu Shankar Pandey created DROOLS-2421: --------------------------------------------- Summary: Unexpected response from rule engine for windowing rules Key: DROOLS-2421 URL: https://issues.jboss.org/browse/DROOLS-2421 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.Final Reporter: Bishnu Shankar Pandey Assignee: Mario Fusco Here the sample code of my window rule : rule "Sliding window test1" agenda-group "g0" when exists Fact( (facts["parameter2"] ) != null && facts["source"] == "A0") && $number: Number() from accumulate(Fact(facts["parameter2"] != null && $t : Double.valueOf(facts["parameter2"]) && facts["source"] == "A0") over window:time(2m) , sum($t)) then globalList.add("2 Minute Sum of parameter2 of Source A0 is " + $number ); end rule "Sliding window test2" agenda-group "g0" when exists Fact( (facts["parameter2"] ) != null && facts["source"] == "A1") && $number: Number() from accumulate(Fact(facts["parameter2"] != null && $t : Double.valueOf(facts["parameter2"]) && facts["source"] == "A1") over window:time(2m) , sum($t)) then globalList.add("2 Minute Sum of parameter2 of Source A1 is " + $number ); end I am sending request from 2 different sources. I am getting response as 0.0 after some time. I check the values in the working memory by using collect as List for the parameter values. I have found that the previous values got deleted when the response is 0.0. I need immediate help. Some important info: Fact is the class Object and it has a Hashmap(facts) as class variable. The factmap contains the variable name as key and its value as variable value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3713) HttpClientURLConnection breaks the TCK

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3713: -------------------------------------- Summary: HttpClientURLConnection breaks the TCK Key: WFCORE-3713 URL: https://issues.jboss.org/browse/WFCORE-3713 Project: WildFly Core Issue Type: Bug Reporter: Stuart Douglas Priority: Blocker As this does not match the behaviour of the JDK HttpUrlConnection some tests in TCK7 no longer work. The particular behaviour in this case is that GET requests are not automatically changed to POST requests if doInput is called, however looking at the class it looks like there is a massive amount of behaviour that is not consistent. This is a big problem, as any customer that is relying on the behaviour of the JDK client have to modify their application. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4822) Consolidate cache store configuration flags into more sensible use case enums

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4822?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4822: --------------------------------- Summary: Consolidate cache store configuration flags into more sensible use case enums (was: Consolidate cache store configuration flags into more sensible use case enums.) > Consolidate cache store configuration flags into more sensible use case enums > ----------------------------------------------------------------------------- > > Key: WFLY-4822 > URL: https://issues.jboss.org/browse/WFLY-4822 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Alpha3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Infinispan cache stores have several boolean flags for defining behavior. There are several combinations of values for these flags that do not make sense (e.g. purge="true" & preload="true" makes no sense). I'd like to consolidate as many of these flags as possible into a set of enumerated values. The enumerated values would more closely map to use cases. This should help eliminate a lot of user confusion. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-81) Create B11 Openshift Cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-81?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo resolved SWSQE-81. ------------------------------------------ Resolution: Done > Create B11 Openshift Cluster > ---------------------------- > > Key: SWSQE-81 > URL: https://issues.jboss.org/browse/SWSQE-81 > Project: Swift Sunshine QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-82) Create B12 Openshift Cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-82?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo resolved SWSQE-82. ------------------------------------------ Resolution: Done > Create B12 Openshift Cluster > ---------------------------- > > Key: SWSQE-82 > URL: https://issues.jboss.org/browse/SWSQE-82 > Project: Swift Sunshine QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10111) Attribute initial size in connector pool configuration must not have a default value

by Flavia Rainone (JIRA)

Flavia Rainone created WFLY-10111: ------------------------------------- Summary: Attribute initial size in connector pool configuration must not have a default value Key: WFLY-10111 URL: https://issues.jboss.org/browse/WFLY-10111 Project: WildFly Issue Type: Bug Components: JCA Reporter: Flavia Rainone Assignee: Flavia Rainone This attribute was assigned a default value by mistake. This change must be reverted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10110) Connector PoolConfigurationRWHandler does not handle undefined values for attributes without default values

by Flavia Rainone (JIRA)

[ https://issues.jboss.org/browse/WFLY-10110?page=com.atlassian.jira.plugin... ] Flavia Rainone updated WFLY-10110: ---------------------------------- Component/s: JCA > Connector PoolConfigurationRWHandler does not handle undefined values for attributes without default values > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-10110 > URL: https://issues.jboss.org/browse/WFLY-10110 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > Currently, the attribute BLOCKING_TIMEOUT_WAIT_MILLIS and INITIAL_POOL_SIZE do not have a default value and require a special treatment for handling undefined values being set. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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