February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2102) Improve deployment annotation parsing error message

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-2102?page=com.atlassian.jira.plugin... ] Lukas Vydra reassigned WFLY-2102: --------------------------------- Assignee: Lukas Vydra > Improve deployment annotation parsing error message > ----------------------------------------------------- > > Key: WFLY-2102 > URL: https://issues.redhat.com/browse/WFLY-2102 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Brad Maxwell > Assignee: Lukas Vydra > Priority: Major > Attachments: test-WFLY-2102.jar > > > Improve deployment annotation parsing error message > Code such as this below, will error with IllegalArgumentException: Empty name segment is not allowed for env. The env is not enough information to identify what the issue is. > @Singleton > @Startup > public class TestEJB { > @Resource(name="/queue/test") > private Queue queue; > } > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for env > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186) > at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:141) > at org.jboss.as.ee.component.OptionalLookupInjectionSource.getResourceValue(OptionalLookupInjectionSource.java:84) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:1019) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:998) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:138) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1062) Created shared libs for repeating stages

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1062: ------------------------------------ Summary: Created shared libs for repeating stages Key: SWSQE-1062 URL: https://issues.redhat.com/browse/SWSQE-1062 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta Stages like login to openshift, clean env, etc. are at many places, we need to start using shared libs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1061) Kiali jenkins dsl refactoring

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1061?page=com.atlassian.jira.plugi... ] Filip Brychta updated SWSQE-1061: --------------------------------- Description: We have lot of repeating code in jenkins dsl. We need to start using shared libs. We could consider - https://stackoverflow.com/questions/53201656/extracting-an-entire-jenkins... More docs - https://jenkins.io/blog/2017/10/02/pipeline-templates-with-shared-libraries/ was:We have lot of repeating code in jenkins dsl. We need to start using shared libs. > Kiali jenkins dsl refactoring > ----------------------------- > > Key: SWSQE-1061 > URL: https://issues.redhat.com/browse/SWSQE-1061 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We have lot of repeating code in jenkins dsl. We need to start using shared libs. > We could consider - https://stackoverflow.com/questions/53201656/extracting-an-entire-jenkins... > More docs - https://jenkins.io/blog/2017/10/02/pipeline-templates-with-shared-libraries/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1061) Kiali jenkins dsl refactoring

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1061: ------------------------------------ Summary: Kiali jenkins dsl refactoring Key: SWSQE-1061 URL: https://issues.redhat.com/browse/SWSQE-1061 Project: Kiali QE Issue Type: Story Reporter: Filip Brychta Assignee: Filip Brychta We have lot of repeating code in jenkins dsl. We need to start using shared libs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1019) Review maistra installation job

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1019?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1019. ---------------------------------- Resolution: Done Downstream job now used new https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/install-jobs/j... which is using OLM. Upstream jobs are still using yamls for now. > Review maistra installation job > ------------------------------- > > Key: SWSQE-1019 > URL: https://issues.redhat.com/browse/SWSQE-1019 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to use correct deployment template based on version for both downstream and upstream builds. This is partially done by https://issues.jboss.org/browse/SWSQE-1017 > Also we might want to consider not using those templates at all for downstream builds and always use OLM. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-12093: ----------------------------------- end time should not change after a job execution is done. {{org.jboss.as.quickstarts.batch.controller.JobData#getEndTime}} should just return the value retrieved from batch job repository to reflect job execution history. > bug in tutorial "batch-processing" with column "End Time" > --------------------------------------------------------- > > Key: WFLY-12093 > URL: https://issues.redhat.com/browse/WFLY-12093 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: batch-processing > Reporter: Святослав Кремлёв > Assignee: Parul Sharma > Priority: Major > Attachments: 2019-05-18 23_16_51-Batch Processing.png > > > in file > org/jboss/as/quickstarts/batch/controller/JobData.java > {code} > public Date getEndTime() { > endTime = new Date(); > return endTime.getTime() == 0 ? null : endTime; > } > {code} > its returns current time every time, not the job endTime -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4993) [DMN Designer] Code Completion - add keywords

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4993?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4993: ------------------------------------ Tester: Jozef Marko Story Points: 2 > [DMN Designer] Code Completion - add keywords > --------------------------------------------- > > Key: DROOLS-4993 > URL: https://issues.redhat.com/browse/DROOLS-4993 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Donato Marrazzo > Assignee: Guilherme Gomes > Priority: Major > Labels: dmn-designer > > Manage FEEL expression keywords: > * in > * or > * and > * between > * if ... then ... else ... > * for ... in ... return ... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5001) [DMN Designer] Data Types - Disable top-right search in the data types page

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-5001: --------------------------------------- Summary: [DMN Designer] Data Types - Disable top-right search in the data types page Key: DROOLS-5001 URL: https://issues.redhat.com/browse/DROOLS-5001 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Attachments: icon.png Disable top-right search in the data types page, since it already has the search bar: !icon.png|width=800! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10715) TransactionSubsystemTestCase does not test for invalid XML in some cases

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/WFLY-10715?page=com.atlassian.jira.plugi... ] Thomas Jenkinson updated WFLY-10715: ------------------------------------ Issue Type: Task (was: Bug) > TransactionSubsystemTestCase does not test for invalid XML in some cases > ------------------------------------------------------------------------ > > Key: WFLY-10715 > URL: https://issues.redhat.com/browse/WFLY-10715 > Project: WildFly > Issue Type: Task > Components: Test Suite, Transactions > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > > 7.0.0+ introduces the following attributes not found in 6.4.0: [use-journal-store, statistics-enabled, journal-store-enable-async-io]. The test xml should be updated to include these and transformers added where missing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5000) Support getContext in Drools' executable model

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5000: ------------------------------------ Summary: Support getContext in Drools' executable model Key: DROOLS-5000 URL: https://issues.redhat.com/browse/DROOLS-5000 Project: Drools Issue Type: Bug Components: executable model Reporter: Luca Molteni Assignee: Luca Molteni jBPM uses this utility method in Knowledge Helper package org.drools.bpmn2 import org.kie.api.runtime.process.ProcessContext rule "Auto-activate Hello1" ruleflow-group "Hello" when then System.out.println(drools); System.out.println(drools.getContext(ProcessContext.class)); System.out.println(drools.getContext(ProcessContext.class).getProcessInstance()); drools.getContext(ProcessContext.class).getProcessInstance().signalEvent("Hello1", null); end -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2020