February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5076) Rule compilation fails with date constraints on nested fact types

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-5076?page=com.atlassian.jira.plug... ] Matteo Casalino updated DROOLS-5076: ------------------------------------ Description: As of Drools 7.32.0.Final, patterns containing constraints on nested dates won't compile. For instance, given the following drl: {noformat} declare Fact n : Nested end declare Nested d : java.util.Date end rule "with nested date" when Fact(n!.d >= "01-Jan-2020", n!.d <= "10-Jan-2020") then end {noformat} we get the following error: {noformat} Message [id=1, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Unable to Analyse Expression n.d >= "01-Jan-2020": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] [Near : {... n.d >= "01-Jan-2020" ....}] ^] Message [id=2, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Unable to Analyse Expression n.d <= "10-Jan-2020": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] [Near : {... n.d <= "10-Jan-2020" ....}] ^] {noformat} We don't reproduce with Drools <= 7.31.0.Final was: As of Drools 7.32.0.Final, patterns containing constraints on nested dates won't compile. For instance, given the following drl: {noformat} declare Fact n : Nested end declare Nested d : java.util.Date end rule "with nested date" when Fact(n!.d >= "01-Jan-2020", n!.d <= "10-Jan-2020") then end {noformat} we get the following error: Message [id=1, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Unable to Analyse Expression n.d >= "01-Jan-2020": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] [Near : {... n.d >= "01-Jan-2020" ....}] ^] Message [id=2, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Unable to Analyse Expression n.d <= "10-Jan-2020": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] [Near : {... n.d <= "10-Jan-2020" ....}] ^] {noformat} We don't reproduce with Drools <= 7.31.0.Final > Rule compilation fails with date constraints on nested fact types > ----------------------------------------------------------------- > > Key: DROOLS-5076 > URL: https://issues.redhat.com/browse/DROOLS-5076 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.32.0.Final, 7.33.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: nested-date-constraint.tgz > > > As of Drools 7.32.0.Final, patterns containing constraints on nested dates won't compile. > For instance, given the following drl: > {noformat} > declare Fact > n : Nested > end > declare Nested > d : java.util.Date > end > rule "with nested date" > when > Fact(n!.d >= "01-Jan-2020", n!.d <= "10-Jan-2020") > then > end > {noformat} > we get the following error: > {noformat} > Message [id=1, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 > text=Unable to Analyse Expression n.d >= "01-Jan-2020": > [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] > [Near : {... n.d >= "01-Jan-2020" ....}] > ^] > Message [id=2, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 > text=Unable to Analyse Expression n.d <= "10-Jan-2020": > [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] > [Near : {... n.d <= "10-Jan-2020" ....}] > ^] > {noformat} > We don't reproduce with Drools <= 7.31.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13121) jgroups channel protocol read-resource error with include-runtime

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-13121?page=com.atlassian.jira.plugi... ] Jean Francois Denise reassigned WFLY-13121: ------------------------------------------- Assignee: Brian Stansberry (was: Paul Ferraro) > jgroups channel protocol read-resource error with include-runtime > ------------------------------------------------------------------ > > Key: WFLY-13121 > URL: https://issues.redhat.com/browse/WFLY-13121 > Project: WildFly > Issue Type: Bug > Components: Clustering, Management > Reporter: Jean Francois Denise > Assignee: Brian Stansberry > Priority: Major > > Start standlone-ha.xml > /subsystem=jgroups/channel=ee/protocol=UDP:read-resource(include-runtime > Client: > { > "outcome" => "failed", > "rolled-back" => true > } > Server: > 12:01:32,541 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("subsystem" => "jgroups"), > ("channel" => "ee"), > ("protocol" => "UDP") > ]) - failure description: "newValue is null" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13121) jgroups channel protocol read-resource error with include-runtime

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-13121: ------------------------------------------- Summary: jgroups channel protocol read-resource error with include-runtime Key: WFLY-13121 URL: https://issues.redhat.com/browse/WFLY-13121 Project: WildFly Issue Type: Bug Components: Clustering, Management Reporter: Jean Francois Denise Assignee: Paul Ferraro Start standlone-ha.xml /subsystem=jgroups/channel=ee/protocol=UDP:read-resource(include-runtime Client: { "outcome" => "failed", "rolled-back" => true } Server: 12:01:32,541 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ ("subsystem" => "jgroups"), ("channel" => "ee"), ("protocol" => "UDP") ]) - failure description: "newValue is null" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5075) [DMN Designer] properties panel is not refreshed for top level output header

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5075?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5075: -------------------------------- Tester: Anna Dupliak (was: Jozef Marko) > [DMN Designer] properties panel is not refreshed for top level output header > ---------------------------------------------------------------------------- > > Key: DROOLS-5075 > URL: https://issues.redhat.com/browse/DROOLS-5075 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: drools-tools > > The issue was found during RHDM-1181 review, however it is probably not related. > The DMN Decision table expression can have complex output - structure/context. In such case output header cells are in two levels. The issue is if the top level output header cell is selected, the properties panel is not refreshed. It is an issue if previously was selected for example input header cell, then after selection change, an inappropriate information is shown in the properties panel. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5075) [DMN Designer] properties panel is not refreshed for top level output header

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5075?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5075: -------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > [DMN Designer] properties panel is not refreshed for top level output header > ---------------------------------------------------------------------------- > > Key: DROOLS-5075 > URL: https://issues.redhat.com/browse/DROOLS-5075 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: drools-tools > > The issue was found during RHDM-1181 review, however it is probably not related. > The DMN Decision table expression can have complex output - structure/context. In such case output header cells are in two levels. The issue is if the top level output header cell is selected, the properties panel is not refreshed. It is an issue if previously was selected for example input header cell, then after selection change, an inappropriate information is shown in the properties panel. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5075) [DMN Designer] properties panel is not refreshed for top level output header

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5075?page=com.atlassian.jira.plug... ] Jozef Marko moved RHDM-1248 to DROOLS-5075: ------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-5075 (was: RHDM-1248) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: DMN Editor (was: Decision Central) Affects Build: (was: CR1) Affects Version/s: 7.34.0.Final (was: 7.7.0.GA) QE Status: NEW > [DMN Designer] properties panel is not refreshed for top level output header > ---------------------------------------------------------------------------- > > Key: DROOLS-5075 > URL: https://issues.redhat.com/browse/DROOLS-5075 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: drools-tools > > The issue was found during RHDM-1181 review, however it is probably not related. > The DMN Decision table expression can have complex output - structure/context. In such case output header cells are in two levels. The issue is if the top level output header cell is selected, the properties panel is not refreshed. It is an issue if previously was selected for example input header cell, then after selection change, an inappropriate information is shown in the properties panel. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5045) [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5045?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5045: ---------------------------------------- Hi [~jomarko] the XML generated for a {{DecisionTable}} when saving a 1.2 model should contain the following: {code} <dmn:decisionTable... > <dmn:input... > ... </dmn:input> <dmn:output... > ... </dmn:output> <dmn:annotation name='Description'/> <dmn:rule... > <dmn:inputEntry... > ... </dmn:inputEntry> <dmn:outputEntry... > ... </dmn:outputEntry> <dmn:annotationEntry> ... </dmn:annotationEntry> </dmn:rule> </dmn:decisionTable... > {code} We don't create ANY {{dmn:annotation}} or {{dmn:annotationEntry}} elements at the moment. > [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation > ------------------------------------------------------------------------------- > > Key: DROOLS-5045 > URL: https://issues.redhat.com/browse/DROOLS-5045 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > DMN1.2 has RuleAnnotation in the DecisionTable expression. > Our marshallers (-backend and -client) do not support it and use the Expression's Description element for the DecisionRule description column. We also need to enhance the UI to support adding/deleting additional RuleAnnotations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13024) Integrate MP Fault Tolerance 2.1

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13024?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13024: ---------------------------------- Description: The gist here being: * SR FT 4.1.x * Eclipse MP FT 2.1 * remove hystrix, hdr, commons-config, rxjava (v1) * update docs Changes in 2.1: https://download.eclipse.org/microprofile/microprofile-fault-tolerance-2.... was: The gist here being: * SR FT 4.1.x * Eclipse MP FT 2.1 * remove hystrix, hdr, commons-config * update docs Changes in 2.1: https://download.eclipse.org/microprofile/microprofile-fault-tolerance-2.... > Integrate MP Fault Tolerance 2.1 > -------------------------------- > > Key: WFLY-13024 > URL: https://issues.redhat.com/browse/WFLY-13024 > Project: WildFly > Issue Type: Feature Request > Components: MP Fault Tolerance > Affects Versions: 19.0.0.Beta1, 19.0.0.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 19.0.0.Beta3, 20.0.0.Beta1 > > > The gist here being: > * SR FT 4.1.x > * Eclipse MP FT 2.1 > * remove hystrix, hdr, commons-config, rxjava (v1) > * update docs > Changes in 2.1: > https://download.eclipse.org/microprofile/microprofile-fault-tolerance-2.... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13120) LayeredDistributionTestCase should cope with an existing layers.conf

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13120: --------------------------------- Summary: LayeredDistributionTestCase should cope with an existing layers.conf Key: WFLY-13120 URL: https://issues.redhat.com/browse/WFLY-13120 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Ingo Weiss Assignee: Brian Stansberry Fix For: 19.0.0.Beta2 LayeredDistributionTestCase writes a layers.conf file but some builds against which this test will run already have one. If that is the case the test should update the existing file instead of discarding its contents. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13119) Support multiple module layers in HostExcludesTestCase

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13119: --------------------------------- Summary: Support multiple module layers in HostExcludesTestCase Key: WFLY-13119 URL: https://issues.redhat.com/browse/WFLY-13119 Project: WildFly Issue Type: Task Components: Management, Test Suite Reporter: Ingo Weiss Assignee: Brian Stansberry Fix For: 19.0.0.Beta3, 20.0.0.Beta1 When HostExcludesTestCase searches for available extensions it should test in other module locations besides system/layers/base. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020