June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4137) KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build

by Justin Holmes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4137?page=com.atlassian.jira.plugi... ] Justin Holmes commented on DROOLS-4137: --------------------------------------- Thank you [~mfusco] for the very quick reply. I think we are just very, very confused by the docs. And for what it's worth, this is the same Justin Holmes that was at Red Hat for many years working with Drools and discussing US politics with you in Barcelona. I'm in a new job now that began a drools evaluation shortly after I joined. Is there a complete example anywhere that we can follow, ideally one that is not tied to Quarkus and also uses XLS decision tables? I see https://github.com/kiegroup/kogito-examples/tree/master/drools-quarkus-ex..., but this is tied to Quarkus. I see https://github.com/kiegroup/drools/blob/master/drools-model/drools-model-... from http://blog.athico.com/2018/02/the-drools-executable-model-is-alive.html but it uses flow DSL. If no such example exists, can you confirm working with XLS decision tables works with the new executable model? If so, we would like to work with you to create an example (perhaps in https://github.com/kiegroup/drools/tree/master/drools-examples?) that can be reused by others and referenced by the docs. > KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build > --------------------------------------------------------------------------------------------- > > Key: DROOLS-4137 > URL: https://issues.jboss.org/browse/DROOLS-4137 > Project: Drools > Issue Type: Bug > Affects Versions: 7.22.0.Final > Reporter: Justin Holmes > Assignee: Mario Fusco > Priority: Major > > I would like to have kie-maven-plugin build the KJar with a serialized KieBase so that it takes less time to boot strap drools. It appears that the maven configuration used by the kie-maven-plugin is broken, or at least there is not sufficient documentation to set it up. > See https://groups.google.com/forum/#!topic/drools-setup/0TZvE5lpcto for more information. > Documentation is VERY limited / scattered in different areas. It probably needs updates. If we can get help to get the build working / bug fixed, we would be happy to submit a doc fix. > We are trying to use drools in a severless environment (though not quite ready for Quarkus). If we are unable to use this build feature, we may be unable to use drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-783) Review and Create new Kiali Install/Deploy Test Cases

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-783: ------------------------------------- Summary: Review and Create new Kiali Install/Deploy Test Cases Key: SWSQE-783 URL: https://issues.jboss.org/browse/SWSQE-783 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Currently there is 1 Polarion Install test case. Review this test case and separate into multiple test cases, as needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-782) Map Jira Queries to Tablue Graphs

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-782: ------------------------------------- Summary: Map Jira Queries to Tablue Graphs Key: SWSQE-782 URL: https://issues.jboss.org/browse/SWSQE-782 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Assignee: Prachi Yadav Map Jira Query to Tableau Graphs, so that we can then validate that the Jira queries are correct. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-781) Create More Descriptive Polarion Run Names

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-781: ------------------------------------- Summary: Create More Descriptive Polarion Run Names Key: SWSQE-781 URL: https://issues.jboss.org/browse/SWSQE-781 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Change the Polarion Run naming from the Kiali version to a more descriptive naming such as "Tech Preview-xx". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4141) Split scesim client module in core and business central modules

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4141: ---------------------------------------- Summary: Split scesim client module in core and business central modules Key: DROOLS-4141 URL: https://issues.jboss.org/browse/DROOLS-4141 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Split the scesim client module in core client (container agnostic) and business-central one (to be used inside Business Central -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4138) Building a KJAR using Decision Table Templates throws NPE

by Carl Mes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4138?page=com.atlassian.jira.plugi... ] Carl Mes commented on DROOLS-4138: ---------------------------------- I have created a PR in the Drools source with a proposed fix: https://github.com/kiegroup/drools/pull/2377 > Building a KJAR using Decision Table Templates throws NPE > --------------------------------------------------------- > > Key: DROOLS-4138 > URL: https://issues.jboss.org/browse/DROOLS-4138 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final, 7.23.0.Final > Reporter: Carl Mes > Assignee: Mario Fusco > Priority: Major > Attachments: DecisionTableConfigurationImpl.java > > > Steps to building a new KJar by defining Resource objects and adding then using KieFileSystem.write(), if a Decision Table Template resource type is added then we get a null pointer exception when the KieBuilder.buildAll() method is invoked. > Sample code that demonstrates this error can be found here: https://github.com/carlmes/decision-table-template, specifically the notes in [TestDecisionTableBuild.java|https://github.com/carlmes/decision-table-tem...]. > Red Hat support case: https://access.redhat.com/support/cases/#/case/02397413 > I have created a proposed fix in [DecisionTableConfigurationImpl.java|https://github.com/kiegroup/drools/bl...], by implementing the missing properties in the fromProperties and toProperties methods. Please see attached updated file that has been tested to fix the issue locally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4138) Building a KJAR using Decision Table Templates throws NPE

by Carl Mes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4138?page=com.atlassian.jira.plugi... ] Carl Mes updated DROOLS-4138: ----------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/2377 > Building a KJAR using Decision Table Templates throws NPE > --------------------------------------------------------- > > Key: DROOLS-4138 > URL: https://issues.jboss.org/browse/DROOLS-4138 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final, 7.23.0.Final > Reporter: Carl Mes > Assignee: Mario Fusco > Priority: Major > Attachments: DecisionTableConfigurationImpl.java > > > Steps to building a new KJar by defining Resource objects and adding then using KieFileSystem.write(), if a Decision Table Template resource type is added then we get a null pointer exception when the KieBuilder.buildAll() method is invoked. > Sample code that demonstrates this error can be found here: https://github.com/carlmes/decision-table-template, specifically the notes in [TestDecisionTableBuild.java|https://github.com/carlmes/decision-table-tem...]. > Red Hat support case: https://access.redhat.com/support/cases/#/case/02397413 > I have created a proposed fix in [DecisionTableConfigurationImpl.java|https://github.com/kiegroup/drools/bl...], by implementing the missing properties in the fromProperties and toProperties methods. Please see attached updated file that has been tested to fix the issue locally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-734) Upload Jaeger TP11 Automation Runs Into Polarion

by Kevin Earls (Jira)

[ https://issues.jboss.org/browse/SWSQE-734?page=com.atlassian.jira.plugin.... ] Kevin Earls resolved SWSQE-734. ------------------------------- Resolution: Done > Upload Jaeger TP11 Automation Runs Into Polarion > ------------------------------------------------ > > Key: SWSQE-734 > URL: https://issues.jboss.org/browse/SWSQE-734 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Kevin Earls > Priority: Major > Labels: pqi > > Using the polarion_uploader, upload Jaeger automation runs into Polarion for TP-11 release. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11601) Weld vs Undertow bootstrap: Race condition

by Matěj Novotný (Jira)

[ https://issues.jboss.org/browse/WFLY-11601?page=com.atlassian.jira.plugin... ] Matěj Novotný commented on WFLY-11601: -------------------------------------- [~grubi] I have drafted a Weld solution [here|https://github.com/manovotn/core/tree/weld2557] that moves bits of bootstrap to earlier phases hence it should avoid the race condition. I've run it through Weld TS, wildfly/testsuite (latest master) and also tried your sample and it worked. But I know your sample was not reproducible for me before so if you could test it, that would be great. If you don't know how to replace versions of Weld in WFLY, I can give you the details. > Weld vs Undertow bootstrap: Race condition > ------------------------------------------ > > Key: WFLY-11601 > URL: https://issues.jboss.org/browse/WFLY-11601 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web (Undertow) > Affects Versions: 15.0.1.Final > Reporter: Stefan Gr > Assignee: Matěj Novotný > Priority: Major > Attachments: TestApp.zip, TestLib.zip, changes.diff, deploy-failed.txt, deploy-mixed-success.txt, deploy-success.txt, test-app-1.0.0.war, weld-core-impl-3.0.5.Final.jar, weld-core-impl-3.0.5.Final.jar > > > WFLY-9732 / WFLY-10784 moves the completion of WELD from the WeldStartService to WeldStartCompetionService. This causes a race condition with the UndertowDeploymentService which executes the servlet listeners for context-initialized which again fires ApplicationScope-initialized events in CDI. > You can find more in [WELD-2557|https://issues.jboss.org/browse/WELD-2557?focusedCommentId=1368...]. > In short: WeldStartCompletionService and UndertowDeploymentService pushes the logic to the executor service. It may happen, that the logik of undertow runs before the weld completion. Events fired in the servlet listeners won't find all event observers. > A possible solution would bo to set the WeldStartCompletionService as a dependency of the UndertowDeploymentService -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11601) Weld vs Undertow bootstrap: Race condition

by Matěj Novotný (Jira)

[ https://issues.jboss.org/browse/WFLY-11601?page=com.atlassian.jira.plugin... ] Matěj Novotný edited comment on WFLY-11601 at 6/6/19 8:49 AM: -------------------------------------------------------------- [~grubi] I have drafted a Weld solution [here|https://github.com/weld/core/pull/1921] that moves bits of bootstrap to earlier phases hence it should avoid the race condition. I've run it through Weld TS, wildfly/testsuite (latest master) and also tried your sample and it worked. But I know your sample was not reproducible for me before so if you could test it, that would be great. If you don't know how to replace versions of Weld in WFLY, I can give you the details. was (Author: manovotn): [~grubi] I have drafted a Weld solution [here|https://github.com/manovotn/core/tree/weld2557] that moves bits of bootstrap to earlier phases hence it should avoid the race condition. I've run it through Weld TS, wildfly/testsuite (latest master) and also tried your sample and it worked. But I know your sample was not reproducible for me before so if you could test it, that would be great. If you don't know how to replace versions of Weld in WFLY, I can give you the details. > Weld vs Undertow bootstrap: Race condition > ------------------------------------------ > > Key: WFLY-11601 > URL: https://issues.jboss.org/browse/WFLY-11601 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web (Undertow) > Affects Versions: 15.0.1.Final > Reporter: Stefan Gr > Assignee: Matěj Novotný > Priority: Major > Attachments: TestApp.zip, TestLib.zip, changes.diff, deploy-failed.txt, deploy-mixed-success.txt, deploy-success.txt, test-app-1.0.0.war, weld-core-impl-3.0.5.Final.jar, weld-core-impl-3.0.5.Final.jar > > > WFLY-9732 / WFLY-10784 moves the completion of WELD from the WeldStartService to WeldStartCompetionService. This causes a race condition with the UndertowDeploymentService which executes the servlet listeners for context-initialized which again fires ApplicationScope-initialized events in CDI. > You can find more in [WELD-2557|https://issues.jboss.org/browse/WELD-2557?focusedCommentId=1368...]. > In short: WeldStartCompletionService and UndertowDeploymentService pushes the logic to the executor service. It may happen, that the logik of undertow runs before the weld completion. Events fired in the servlet listeners won't find all event observers. > A possible solution would bo to set the WeldStartCompletionService as a dependency of the UndertowDeploymentService -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019