August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1705) Audit remaining Class.forName in static factory methods

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1705?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-1705: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 32-34 (was: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31) > Audit remaining Class.forName in static factory methods > ------------------------------------------------------- > > Key: DROOLS-1705 > URL: https://issues.jboss.org/browse/DROOLS-1705 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Matteo Mortari > Assignee: Edoardo Vacchi > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1705) Audit remaining Class.forName in static factory methods

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1705?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-1705: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 32-34) > Audit remaining Class.forName in static factory methods > ------------------------------------------------------- > > Key: DROOLS-1705 > URL: https://issues.jboss.org/browse/DROOLS-1705 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Matteo Mortari > Assignee: Edoardo Vacchi > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3923: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 32-34 (was: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31) > (C)DI detection should be more reliable/standard for codegen > ------------------------------------------------------------ > > Key: DROOLS-3923 > URL: https://issues.jboss.org/browse/DROOLS-3923 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is > (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application > We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better. > Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4346) Provide fixed code for Kie Client usage in docs

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4346?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4346: ----------------------------------- Sprint: 2019 Week 32-34 (was: 2019 Week 29-31) > Provide fixed code for Kie Client usage in docs > ----------------------------------------------- > > Key: DROOLS-4346 > URL: https://issues.jboss.org/browse/DROOLS-4346 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > https://issues.jboss.org/browse/BXMSDOC-4259 code for client usage does not compile, throws exception -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4269) kogito-codegen-tests: alternative testing strategy for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4269?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4269: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 32-34 (was: 2019 Week 26-28, 2019 Week 29-31) > kogito-codegen-tests: alternative testing strategy for codegen > -------------------------------------------------------------- > > Key: DROOLS-4269 > URL: https://issues.jboss.org/browse/DROOLS-4269 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, kogito, submarine > > Currently we are doing dynamic compilation and classloading to test code generation. I am proposing an alternative strategy that use the plain Maven plugin. > - create `kogito-codegen-tests` > - write data/rules/process sources under src/main/{java,resources} > - write tests under src/test/ > tests are now allowed to refer directly to codegenerated classes by name. > just use mvn compile test to run the tests > caveat: not sure if the maven plugin is picked up from the current source tree or from the SNAPSHOT on the nexus, we need to check this -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4189) Kogito Rules Getting Started

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4189?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4189: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 32-34 (was: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31) > Kogito Rules Getting Started > ---------------------------- > > Key: DROOLS-4189 > URL: https://issues.jboss.org/browse/DROOLS-4189 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, kogito, submarine > Fix For: 8.0.0.Final > > > add README.md / asciidoc about getting started with Drools inside Kogito -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4400) Can not open a Scenario Simulation model version 1.5

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4400?page=com.atlassian.jira.plugi... ] Gabriele Cardosi reassigned DROOLS-4400: ---------------------------------------- Assignee: Gabriele Cardosi (was: Daniele Zonca) > Can not open a Scenario Simulation model version 1.5 > ---------------------------------------------------- > > Key: DROOLS-4400 > URL: https://issues.jboss.org/browse/DROOLS-4400 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Critical > Attachments: PlaneBoarding3629284258846927242.zip, Screenshot from 2019-08-05 09-39-26.png, error.log > > > The latest version (1.6) of Scenario Simulation model is not compatible with previous Scenario Simulation model (1.5). If user tries to open Scenario Simulation created on older product version, an error is thrown. For more detail see the attache Plane Boarding project. There are *.scesim* files with Scenario Simulation model version 1.5, however they can not be opened in business central that has the latest Scenario Simulation model version 1.6. > h2. Reproducer/Accepetance test > https://github.com/jboss-integration/bxms-qe-tests/blob/master/test-kie-w... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4400) Can not open a Scenario Simulation model version 1.5

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4400?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4400: -------------------------------- Description: The latest version (1.6) of Scenario Simulation model is not compatible with previous Scenario Simulation model (1.5). If user tries to open Scenario Simulation created on older product version, an error is thrown. For more detail see the attache Plane Boarding project. There are *.scesim* files with Scenario Simulation model version 1.5, however they can not be opened in business central that has the latest Scenario Simulation model version 1.6. h2. Reproducer/Accepetance test https://github.com/jboss-integration/bxms-qe-tests/blob/master/test-kie-w... was:The latest version (1.6) of Scenario Simulation model is not compatible with previous Scenario Simulation model (1.5). If user tries to open Scenario Simulation created on older product version, an error is thrown. For more detail see the attache Plane Boarding project. There are *.scesim* files with Scenario Simulation model version 1.5, however they can not be opened in business central that has the latest Scenario Simulation model version 1.6. > Can not open a Scenario Simulation model version 1.5 > ---------------------------------------------------- > > Key: DROOLS-4400 > URL: https://issues.jboss.org/browse/DROOLS-4400 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Critical > Attachments: PlaneBoarding3629284258846927242.zip, Screenshot from 2019-08-05 09-39-26.png, error.log > > > The latest version (1.6) of Scenario Simulation model is not compatible with previous Scenario Simulation model (1.5). If user tries to open Scenario Simulation created on older product version, an error is thrown. For more detail see the attache Plane Boarding project. There are *.scesim* files with Scenario Simulation model version 1.5, however they can not be opened in business central that has the latest Scenario Simulation model version 1.6. > h2. Reproducer/Accepetance test > https://github.com/jboss-integration/bxms-qe-tests/blob/master/test-kie-w... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4400) Can not open a Scenario Simulation model version 1.5

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4400?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4400: -------------------------------- Tester: Jozef Marko > Can not open a Scenario Simulation model version 1.5 > ---------------------------------------------------- > > Key: DROOLS-4400 > URL: https://issues.jboss.org/browse/DROOLS-4400 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Critical > Attachments: PlaneBoarding3629284258846927242.zip, Screenshot from 2019-08-05 09-39-26.png, error.log > > > The latest version (1.6) of Scenario Simulation model is not compatible with previous Scenario Simulation model (1.5). If user tries to open Scenario Simulation created on older product version, an error is thrown. For more detail see the attache Plane Boarding project. There are *.scesim* files with Scenario Simulation model version 1.5, however they can not be opened in business central that has the latest Scenario Simulation model version 1.6. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4400) Can not open a Scenario Simulation model version 1.5

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4400?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4400: -------------------------------- Attachment: error.log > Can not open a Scenario Simulation model version 1.5 > ---------------------------------------------------- > > Key: DROOLS-4400 > URL: https://issues.jboss.org/browse/DROOLS-4400 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Critical > Attachments: PlaneBoarding3629284258846927242.zip, Screenshot from 2019-08-05 09-39-26.png, error.log > > > The latest version (1.6) of Scenario Simulation model is not compatible with previous Scenario Simulation model (1.5). If user tries to open Scenario Simulation created on older product version, an error is thrown. For more detail see the attache Plane Boarding project. There are *.scesim* files with Scenario Simulation model version 1.5, however they can not be opened in business central that has the latest Scenario Simulation model version 1.6. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 August 2019