May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5168) Collection editor for List of Enums

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5168?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5168: ------------------------------- Fix Version/s: 7.39.0.Final > Collection editor for List of Enums > ----------------------------------- > > Key: DROOLS-5168 > URL: https://issues.redhat.com/browse/DROOLS-5168 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Fix For: 7.39.0.Final > > Attachments: MySpace_project.zip, Screenshot from 2020-03-09 16-06-05.png > > > There is issue in Test Scenarios when user invokes the collection editor for {{java.util.List<MyEnum>}} field. > {code}Uncaught exception: (TypeError) : Cannot read property 'getSimpleProperties_1_g$' of null {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5331) Support for Enums in Rule Test Scenario

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5331?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5331: ------------------------------- Fix Version/s: 7.39.0.Final > Support for Enums in Rule Test Scenario > --------------------------------------- > > Key: DROOLS-5331 > URL: https://issues.redhat.com/browse/DROOLS-5331 > Project: Drools > Issue Type: Feature Request > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Fix For: 7.39.0.Final > > Attachments: Customer.java, EnumTest.java > > > Currently, Test Scenario doesn't support an attribute of Enumeration type. > In case of RULE Scenario: > Loading a Data Object with such attribute, will result in Complex Type properties with a nested simple property "declaringClass" of "java.lang.Class" type. > The expected result should be a Simple property of Enum type (in this case: category [java.lang.Enum] ) > In case of DMN Scenario: > Currently no impacts -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5078) can't test against bigdecimal value in test scenario in business central

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5078?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5078: ------------------------------- Fix Version/s: 7.39.0.Final > can't test against bigdecimal value in test scenario in business central > ------------------------------------------------------------------------ > > Key: DROOLS-5078 > URL: https://issues.redhat.com/browse/DROOLS-5078 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Werner Van Herrewegen > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Fix For: 7.39.0.Final > > Attachments: image-2020-02-19-10-13-01-440.png > > > I get the error : test failed with reason > !image-2020-02-19-10-13-01-440.png|thumbnail! > see screenshot > 'class.java.math.bigdecimal is not supported' -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5389) Create single abstract class for integration tests in new PMML implementation

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5389: ------------------------------------ Summary: Create single abstract class for integration tests in new PMML implementation Key: DROOLS-5389 URL: https://issues.redhat.com/browse/DROOLS-5389 Project: Drools Issue Type: Task Reporter: Jiri Petrlik Assignee: Jiri Petrlik Currently there are multiple abstract classes for PMML integration tests such as AbstractPMMLTreeTest, AbstractPMMLRegressionTest etc. The goal of this JIRA is to unify them and create one single abstract class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13257) Improvements for MicroProfile Fault Tolerance quickstart

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13257?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13257: ---------------------------------- Priority: Optional (was: Major) > Improvements for MicroProfile Fault Tolerance quickstart > -------------------------------------------------------- > > Key: WFLY-13257 > URL: https://issues.redhat.com/browse/WFLY-13257 > Project: WildFly > Issue Type: Task > Components: MP Fault Tolerance, Quickstarts > Affects Versions: 19.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: Awaiting Volunteers > > > Follow up on WFLY-12770 – the initial implementation: > * Investigate/update OpenShift Support > * Include a test case (I have a local unfinished branch) > * Demonstrate @Bulkhead > * Demonstrate @Asynchronous -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5388) Eclipse Rule Editor does not recognize Java source level

by Stefan Winkler (Jira)

[ https://issues.redhat.com/browse/DROOLS-5388?page=com.atlassian.jira.plug... ] Stefan Winkler updated DROOLS-5388: ----------------------------------- Steps to Reproduce: # Using the Eclipse Installer, install Eclipse for Java and DSL developers 2020-03 or 2020-06. # Then install the org.drools.eclipse plugin from https://download.jboss.org/drools/release/7.36.0.Final/org.drools.updates... # Create a new Drools Project (File > New > Project > Drools Project) and select the option to generate the project using sample files. # Open drools-test/src/main/resources/com/sample/rules/Sample.drl in the Rule Editor. # To the {{then}} block add the following line of code and save the file: {{Stream.of(m).forEach(System.out::println);}} *Expected:* no error marker appears *Observed:* error marker appears saying the lambdas can only be used in source level 1.8+ was: # Using the Eclipse Installer, install Eclipse for Java and DSL developers 2020-03 or 2020-06. # Then install the org.drools.eclipse plugin from https://download.jboss.org/drools/release/7.36.0.Final/org.drools.updates... # Create a new Drools Project (File > New > Project > Drools Project) and select the option to generate the project using sample files. # Open drools-test/src/main/resources/com/sample/rules/Sample.drl in the Rule Editor. # To the `then` block add the following line of code and save the file: `Stream.of(m).forEach(System.out::println);` *Expected:* no error marker appears *Observed:* error marker appears saying the lambdas can only be used in source level 1.8+ > Eclipse Rule Editor does not recognize Java source level > -------------------------------------------------------- > > Key: DROOLS-5388 > URL: https://issues.redhat.com/browse/DROOLS-5388 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.36.0.Final > Reporter: Stefan Winkler > Assignee: Kris Verlaenen > Priority: Major > > See this stackoverflow: > https://stackoverflow.com/q/62062516/2239897 > In an Eclipse 2020-03 or 2020-06 installation, when the org.drools.eclipse 7.36.0.Final plugin is installed, a .drl file containing Java 1.5+ source code shows error markers about unsupported Java syntax. > Plugin org.drools.eclipse version 7.21.0.Final with an otherwise identical Eclipse installation works fine. There seems to be a regression introduced somewhere between 7.21.0 and 7.36.0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5388) Eclipse Rule Editor does not recognize Java source level

by Stefan Winkler (Jira)

Stefan Winkler created DROOLS-5388: -------------------------------------- Summary: Eclipse Rule Editor does not recognize Java source level Key: DROOLS-5388 URL: https://issues.redhat.com/browse/DROOLS-5388 Project: Drools Issue Type: Bug Components: eclipse plugin Affects Versions: 7.36.0.Final Reporter: Stefan Winkler Assignee: Kris Verlaenen See this stackoverflow: https://stackoverflow.com/q/62062516/2239897 In an Eclipse 2020-03 or 2020-06 installation, when the org.drools.eclipse 7.36.0.Final plugin is installed, a .drl file containing Java 1.5+ source code shows error markers about unsupported Java syntax. Plugin org.drools.eclipse version 7.21.0.Final with an otherwise identical Eclipse installation works fine. There seems to be a regression introduced somewhere between 7.21.0 and 7.36.0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13532) Dependency version substitutions in MP Quickstarts README.adoc

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-13532: -------------------------------------- Summary: Dependency version substitutions in MP Quickstarts README.adoc Key: WFLY-13532 URL: https://issues.redhat.com/browse/WFLY-13532 Project: WildFly Issue Type: Enhancement Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins Most Microprofile Quickstarts have a section for user to build the app from scratch, which requires setting up the project's dependency versions as properties, and this enhancement should add automatically substitution for such versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-13051: -------------------------------------------- [~nimo22] Can you please provide the steps to recreate this issue? > provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService > ------------------------------------------------------------------ > > Key: WFLY-13051 > URL: https://issues.redhat.com/browse/WFLY-13051 > Project: WildFly > Issue Type: Enhancement > Components: Concurrency Utilities > Affects Versions: 19.0.0.Beta1 > Reporter: nimo stephan > Assignee: Eduardo Martins > Priority: Major > > Using > {code:java} > @Resource > private ManagedScheduledExecutorService executor; > {code} > provides no possiblity to setRemoveOnCancelPolicy to true. > A casting within a method: > {code:java} > ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); > {code} > throws the error: > {code:java} > Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap') > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) > {code} > Please provide option to cast or if not possible to add the property > {code:java} > setRemoveOnCancelPolicy() > {code} > within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)". -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty updated WFLY-13051: --------------------------------------- Comment: was deleted (was: [~nimo22] Can you please provide the steps to recreate this issue?) > provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService > ------------------------------------------------------------------ > > Key: WFLY-13051 > URL: https://issues.redhat.com/browse/WFLY-13051 > Project: WildFly > Issue Type: Enhancement > Components: Concurrency Utilities > Affects Versions: 19.0.0.Beta1 > Reporter: nimo stephan > Assignee: Eduardo Martins > Priority: Major > > Using > {code:java} > @Resource > private ManagedScheduledExecutorService executor; > {code} > provides no possiblity to setRemoveOnCancelPolicy to true. > A casting within a method: > {code:java} > ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); > {code} > throws the error: > {code:java} > Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap') > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) > {code} > Please provide option to cast or if not possible to add the property > {code:java} > setRemoveOnCancelPolicy() > {code} > within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)". -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 12 months

1
0
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2020