May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3680) Explore HA CEP design and architecture

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3680?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3680: ----------------------------------- Sprint: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22 (was: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19) > Explore HA CEP design and architecture > -------------------------------------- > > Key: DROOLS-3680 > URL: https://issues.jboss.org/browse/DROOLS-3680 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3569) Configure SonarCloud for Drools

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3569?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3569: ----------------------------------- Sprint: 2019 Week 05-07, 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22 (was: 2019 Week 05-07, 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19) > Configure SonarCloud for Drools > ------------------------------- > > Key: DROOLS-3569 > URL: https://issues.jboss.org/browse/DROOLS-3569 > Project: Drools > Issue Type: Story > Components: build > Reporter: Radovan Synek > Assignee: Radovan Synek > Priority: Major > Fix For: 7.22.0.Final > > > Configure SonarCloud analysis of PRs in Drools repository. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3727) [DMN Designer] Quick Silver: Minimal standalone preparation

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3727?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3727: ----------------------------------- Sprint: 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22 (was: 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19) > [DMN Designer] Quick Silver: Minimal standalone preparation > ----------------------------------------------------------- > > Key: DROOLS-3727 > URL: https://issues.jboss.org/browse/DROOLS-3727 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: Stunner, drools-tools, submarine > Fix For: 8.0.0.Final > > > Prepare a minimal DMN Designer standalone WAR that only supports _standalone_ mode. > No Home Page, no Library, No preferences, no other editors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3015) [DMN Designer] Prohibit parallel item definition edition

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3015?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3015: ----------------------------------- Sprint: 2019 Week 17-19, 2019 Week 20-22 (was: 2019 Week 17-19) > [DMN Designer] Prohibit parallel item definition edition > -------------------------------------------------------- > > Key: DROOLS-3015 > URL: https://issues.jboss.org/browse/DROOLS-3015 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-09-24 13-00-45.png > > > We should prohibit parallel edit operation of item definitions in managa custom data type dialog. It brings troubles in different scenarios: > h2. Save parent item > # Open attached dmn model > # Invoke manage custom data type dialog > # Expand *tProfile* item > # Click on edit next to *tProfile (Structure)* > # Click on edit next to *Name (string)* > # Change *Name* to *Name_updated* > # Change *tProfile* to *tProfile_updated* > # Click *Save* next *tProfile_updated* > # Save button for *Name_updated* will disappear > # Changes saved just for parent item *tProfile_updated* > h2. Save referred items > # Open attached dmn model > # Invoke manage custom data type dialog > # Click on edit next to *tGender (string)* > # Click on edit next to *tGenders (tGender)* > # Rename *tGender* to *tGender_updated* > # Click *Save* next *tGender_updated* > # The data type select box for *tGenders* will disappear, see > ## !Screenshot from 2018-09-24 13-00-45.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3840) Extend Rule runner to support additional parameters

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3840?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3840: ----------------------------------- Sprint: 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22 (was: 2019 Week 14-16, 2019 Week 17-19) > Extend Rule runner to support additional parameters > --------------------------------------------------- > > Key: DROOLS-3840 > URL: https://issues.jboss.org/browse/DROOLS-3840 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use these rule parameters > https://issues.jboss.org/browse/DROOLS-3572 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Fabio Bonfante (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Fabio Bonfante edited comment on DROOLS-1540 at 5/13/19 8:51 AM: ----------------------------------------------------------------- I add just two cents on the "issue" sharing my experience on another corner-case... (sadly) Java serialization. I was able to use the documented work-around, I've a spring-devtools.properties with: {noformat} restart.include.drools-core=/drools-core-7.0.0.Final.jar restart.include.drools-compiler=/drools-compiler-7.0.0.Final.jar restart.include.kie-api=/kie-api-7.0.0.Final.jar restart.include.kie-ci=/kie-ci-7.0.0.Final.jar restart.include.kie-internal=/kie-internal-7.0.0.Final.jar {noformat} But in a rule using java serialization, I got an amazing: {noformat} Caused by: java.lang.ClassCastException: com.example.OrderREO cannot be cast to com.example.OrderREO at rules.com.example.CloneWithServiceCode.cloneWithServiceCode(CloneWithServiceCode.java:55) ~[na:na] at rules.com.example.Rule_My_Rule_621849765706.defaultConsequence(My_Rule_621849765706.java:9) ~[na:na] at rules.com.example.Rule_My_Rule_621849765706DefaultConsequenceInvokerGenerated.evaluate(Unknown Source) ~[na:na] at rules.com.example.Rule_My_Rule_621849765706DefaultConsequenceInvoker.evaluate(Unknown Source) ~[na:na] at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:431) ~[drools-core-7.0.0.Final.jar:7.0.0.Final] ... 129 common frames omitted {noformat} Given that I'll have to wipe-out every form of Java Serialization from the rules... (the Object.clone() was so tempting for our business-rules team... and they didn't knows the drawbacks) I would like to know if I missed to specify some jar in the spring-devtools.properties. Thank's in advance. was (Author: fabio.bonfante): I add just two cents on the "issue" sharing my experience on another corner-case... (sadly) Java serialization. I was able to use the documented work-around, I've a spring-devtools.properties with: {{restart.include.drools-core=/drools-core-7.0.0.Final.jar restart.include.drools-compiler=/drools-compiler-7.0.0.Final.jar restart.include.kie-api=/kie-api-7.0.0.Final.jar restart.include.kie-ci=/kie-ci-7.0.0.Final.jar restart.include.kie-internal=/kie-internal-7.0.0.Final.jar }} But in a rule using java serialization, I got an amazing: {{Caused by: java.lang.ClassCastException: com.example.OrderREO cannot be cast to com.example.OrderREO at rules.com.example.CloneWithServiceCode.cloneWithServiceCode(CloneWithServiceCode.java:55) ~[na:na] at rules.com.example.Rule_My_Rule_621849765706.defaultConsequence(My_Rule_621849765706.java:9) ~[na:na] at rules.com.example.Rule_My_Rule_621849765706DefaultConsequenceInvokerGenerated.evaluate(Unknown Source) ~[na:na] at rules.com.example.Rule_My_Rule_621849765706DefaultConsequenceInvoker.evaluate(Unknown Source) ~[na:na] at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:431) ~[drools-core-7.0.0.Final.jar:7.0.0.Final] ... 129 common frames omitted}} Given that I'll have to wipe-out every form of Java Serialization from the rules... (the Object.clone() was so tempting for our business-rules team... and they didn't knows the drawbacks) I would like to know if I missed to specify some jar in the spring-devtools.properties. Thank's in advance. > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.20.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Fabio Bonfante (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Fabio Bonfante commented on DROOLS-1540: ---------------------------------------- Another, maybe, useful update on using the workaround. The blamed serialization code in the rule was: {code:java} OrderREO newOrder = (OrderREO) SerializationUtils.clone(order); {code} So, I tried adding the jar to the {{spring-devtools.properties}} (apache commons-lang-2.4 in my case), {noformat} restart.include.commons-lang2=/commons-lang-2.4.jar {noformat} and it worked. > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.20.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-736) Create OCP4.1 Cluster on Bare Metal

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-736?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-736: ---------------------------------- Summary: Create OCP4.1 Cluster on Bare Metal (was: Create OC4.1 Cluster on Bare Metal ) > Create OCP4.1 Cluster on Bare Metal > ------------------------------------ > > Key: SWSQE-736 > URL: https://issues.jboss.org/browse/SWSQE-736 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > OC4.1 now supports bare metal. > https://github.com/openshift/installer/releases -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-736) Create OC4.1 Cluster on Bare Metal

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-736: ------------------------------------- Summary: Create OC4.1 Cluster on Bare Metal Key: SWSQE-736 URL: https://issues.jboss.org/browse/SWSQE-736 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney OC4.1 now supports bare metal. https://github.com/openshift/installer/releases -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4469) Upgrade Remoting JMX to 3.0.2.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4469: ---------------------------------------- Summary: Upgrade Remoting JMX to 3.0.2.Final Key: WFCORE-4469 URL: https://issues.jboss.org/browse/WFCORE-4469 Project: WildFly Core Issue Type: Component Upgrade Components: JMX Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.CR1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 May 2019