April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5284) MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5284?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-5284: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Mario Fusco) > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > ---------------------------------------------------------- > > Key: DROOLS-5284 > URL: https://issues.redhat.com/browse/DROOLS-5284 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.36.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > {noformat} > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.97 s <<< FAILURE! - in org.drools.compiler.integrationtests.MVELTest > [ERROR] testTypeCoercionLongDivByInt(org.drools.compiler.integrationtests.MVELTest) Time elapsed: 0.962 s <<< FAILURE! > java.lang.AssertionError: expected:<7.350000> but was:<7> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.drools.compiler.integrationtests.MVELTest.testTypeCoercionLongDivByInt(MVELTest.java:1150) > ... > [INFO] > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] MVELTest.testTypeCoercionLongDivByInt:1150 expected:<7.350000> but was:<7> > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5284) MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5284: ----------------------------------------- Summary: MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 Key: DROOLS-5284 URL: https://issues.redhat.com/browse/DROOLS-5284 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.36.0.Final Reporter: Toshiya Kobayashi Assignee: Mario Fusco MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 {noformat} [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.97 s <<< FAILURE! - in org.drools.compiler.integrationtests.MVELTest [ERROR] testTypeCoercionLongDivByInt(org.drools.compiler.integrationtests.MVELTest) Time elapsed: 0.962 s <<< FAILURE! java.lang.AssertionError: expected:<7.350000> but was:<7> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.drools.compiler.integrationtests.MVELTest.testTypeCoercionLongDivByInt(MVELTest.java:1150) ... [INFO] [INFO] Results: [INFO] [ERROR] Failures: [ERROR] MVELTest.testTypeCoercionLongDivByInt:1150 expected:<7.350000> but was:<7> {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4952) Give a better error message for standard configuration tests

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4952?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-4952: ---------------------------------- Priority: Minor (was: Major) > Give a better error message for standard configuration tests > ------------------------------------------------------------ > > Key: WFCORE-4952 > URL: https://issues.redhat.com/browse/WFCORE-4952 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > The {{StandardConfigsXMLValidationUnitTestCase}} tests validate the default configuration files. These are written into a file as a single line. This makes it a little more difficult to determine where the error is. > A simple fix for this is to just write a new line after each line. This will give a better error message as to which line the issue is one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4952) Give a better error message for standard configuration tests

by James Perkins (Jira)

James Perkins created WFCORE-4952: ------------------------------------- Summary: Give a better error message for standard configuration tests Key: WFCORE-4952 URL: https://issues.redhat.com/browse/WFCORE-4952 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Reporter: James Perkins Assignee: James Perkins The {{StandardConfigsXMLValidationUnitTestCase}} tests validate the default configuration files. These are written into a file as a single line. This makes it a little more difficult to determine where the error is. A simple fix for this is to just write a new line after each line. This will give a better error message as to which line the issue is one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5280) List Filter expression returning single item and nested within arithmetic expression fails to evaluate

by Tracy Hires (Jira)

[ https://issues.redhat.com/browse/DROOLS-5280?page=com.atlassian.jira.plug... ] Tracy Hires commented on DROOLS-5280: ------------------------------------- Yes, you're right. I see that the dmn spec in v1.3 made it clear that the FEEL that I've expected to work is not supported. I had missed both the update in the dmn spec and that the reported version of the dmn engine comforms with v1.3. (I'm not positive whether that semantic did work in earlier versions of the redhat dmn engine, but I suspect it did, as I remember finding the automatic conversion of a singleton list to a single instance to be a convenient shorthand) Thank you for taking the time to offer a complete explanation. > List Filter expression returning single item and nested within arithmetic expression fails to evaluate > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-5280 > URL: https://issues.redhat.com/browse/DROOLS-5280 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.34.0.Final, 7.36.0.Final > Reporter: Tracy Hires > Assignee: Matteo Mortari > Priority: Major > Attachments: MySpace_Relation.zip, screenshot-1.png, screenshot-2.png, screenshot-3.png > > > the expression `addend + listOfStructure[field1="some value"].numberField`, where `field1="some value"` filters `listOfStructure` to a single item and `addend` and `numberField` are both non-null numbers, fails to evaluate. It's possible to work around this by placing `listOfStructure[field1="some value"]` into a separate decision. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13417) Optimize marshalling of EnumMap and EnumSet

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13417?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13417: -------------------------------- Summary: Optimize marshalling of EnumMap and EnumSet (was: Optimize marshalling of EnumSet) > Optimize marshalling of EnumMap and EnumSet > ------------------------------------------- > > Key: WFLY-13417 > URL: https://issues.redhat.com/browse/WFLY-13417 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 19.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5097) @Startup @Singleton Beans Constructed Multiple Times

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-5097?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos commented on WFLY-5097: ----------------------------------------------- Adding the mvtc : https://github.com/jboss-set/eap-additional-testsuite/pull/138 > @Startup @Singleton Beans Constructed Multiple Times > ---------------------------------------------------- > > Key: WFLY-5097 > URL: https://issues.redhat.com/browse/WFLY-5097 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.1.Final > Environment: All > Reporter: Davide Crudo > Assignee: Panagiotis Sotiropoulos > Priority: Major > Attachments: singleton.zip > > > When using @Startup and/or @Singleton to start a Bean on server startup, everytime a method is accessed or the bean is injected with @EJB, both Constructor and @Postconstruct are executed. > This happens multiple times, each time any component uses the Singleton bean. > This seems similar to an issue reported for JBOSS AS 7.x (see forum link reference below) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13418) Optimize marshalling of blocking queues

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13418: ----------------------------------- Summary: Optimize marshalling of blocking queues Key: WFLY-13418 URL: https://issues.redhat.com/browse/WFLY-13418 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 19.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13417) Optimize marshalling of EnumSet

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13417: ----------------------------------- Summary: Optimize marshalling of EnumSet Key: WFLY-13417 URL: https://issues.redhat.com/browse/WFLY-13417 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 19.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13416) Upgrade jberet-core from 1.3.5.Final to 1.3.6.Final

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13416?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFLY-13416: ------------------------------ Description: Diff between jberet-core 1.3.5.Final and 1.3.6.Final: https://github.com/jberet/jsr352/compare/1.3.5.Final...1.3.6.Final The issue fixed in this release: was:Diff between jberet-core 1.3.5.Final and 1.3.6.Final: https://github.com/jberet/jsr352/compare/1.3.5.Final...1.3.6.Final > Upgrade jberet-core from 1.3.5.Final to 1.3.6.Final > --------------------------------------------------- > > Key: WFLY-13416 > URL: https://issues.redhat.com/browse/WFLY-13416 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > > Diff between jberet-core 1.3.5.Final and 1.3.6.Final: https://github.com/jberet/jsr352/compare/1.3.5.Final...1.3.6.Final > The issue fixed in this release: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 April 2020