August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4407) [DMN Designer] Search feature - Highlight the current result with colors that follow the PF standard

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4407?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4407: -------------------------------- Tester: Jozef Marko > [DMN Designer] Search feature - Highlight the current result with colors that follow the PF standard > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-4407 > URL: https://issues.jboss.org/browse/DROOLS-4407 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > All places (_DMN Boxed expressions editor, Guided Decision Tables editor, Guided Decision Tables graph editor, and DMN Data Types tab_) that use the search component must follow the PatternFly standard colors to highlight the cells. > Apply the infrastructure code from https://issues.jboss.org/browse/DROOLS-4406 to highlight the grid cells, and pure CSS to highlight the Data Types. > BG: #F9D67A > Stroke: #F5C12E > ⚠️ Notice: > The DMN graph stay as is for now. Since nodes can have their own colors, the current highlight is enough. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-169) Galleon provisioning does not work when layers defined using env vars

by Nikoleta Ziakova (Jira)

[ https://issues.jboss.org/browse/WFWIP-169?page=com.atlassian.jira.plugin.... ] Nikoleta Ziakova updated WFWIP-169: ----------------------------------- Priority: Critical (was: Major) > Galleon provisioning does not work when layers defined using env vars > --------------------------------------------------------------------- > > Key: WFWIP-169 > URL: https://issues.jboss.org/browse/WFWIP-169 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Nikoleta Ziakova > Assignee: Jean Francois Denise > Priority: Critical > > When running s2i build using the builder [image|docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7...] and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: > {code} > oc new-app --template=eap-cd-basic-s2i \ > -p IMAGE_STREAM_NAMESPACE=eap-demo \ > -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ > -p SOURCE_REPOSITORY_REF=test \ > -p CONTEXT_DIR=kitchensink \ > -p APPLICATION_NAME=kitchensink \ > -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource > # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 > {code} > {code} > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] > {code} > When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. > This blocks our testing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-169) Galleon provisioning does not work when layers defined using env vars

by Nikoleta Ziakova (Jira)

[ https://issues.jboss.org/browse/WFWIP-169?page=com.atlassian.jira.plugin.... ] Nikoleta Ziakova updated WFWIP-169: ----------------------------------- Description: When running s2i build using the builder [image|docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7...] and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: {code} oc new-app --template=eap-cd-basic-s2i \ -p IMAGE_STREAM_NAMESPACE=eap-demo \ -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ -p SOURCE_REPOSITORY_REF=test \ -p CONTEXT_DIR=kitchensink \ -p APPLICATION_NAME=kitchensink \ -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 {code} {code} WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] {code} When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. This blocks our testing. was: When running s2i build using the builder [image|docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7...] and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: {code} oc new-app --template=eap-cd-basic-s2i \ -p IMAGE_STREAM_NAMESPACE=eap-demo \ -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ -p SOURCE_REPOSITORY_REF=test \ -p CONTEXT_DIR=kitchensink \ -p APPLICATION_NAME=kitchensink \ -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 {code} {code} WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] {code} When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. > Galleon provisioning does not work when layers defined using env vars > --------------------------------------------------------------------- > > Key: WFWIP-169 > URL: https://issues.jboss.org/browse/WFWIP-169 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Nikoleta Ziakova > Assignee: Jean Francois Denise > Priority: Major > > When running s2i build using the builder [image|docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7...] and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: > {code} > oc new-app --template=eap-cd-basic-s2i \ > -p IMAGE_STREAM_NAMESPACE=eap-demo \ > -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ > -p SOURCE_REPOSITORY_REF=test \ > -p CONTEXT_DIR=kitchensink \ > -p APPLICATION_NAME=kitchensink \ > -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource > # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 > {code} > {code} > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] > {code} > When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. > This blocks our testing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-169) Galleon provisioning does not work when layers defined using env vars

by Nikoleta Ziakova (Jira)

Nikoleta Ziakova created WFWIP-169: -------------------------------------- Summary: Galleon provisioning does not work when layers defined using env vars Key: WFWIP-169 URL: https://issues.jboss.org/browse/WFWIP-169 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Nikoleta Ziakova Assignee: Jean Francois Denise When running s2i build using the builder [image|docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7...] and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: {code} oc new-app --template=eap-cd-basic-s2i \ -p IMAGE_STREAM_NAMESPACE=eap-demo \ -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ -p SOURCE_REPOSITORY_REF=test \ -p CONTEXT_DIR=kitchensink \ -p APPLICATION_NAME=kitchensink \ -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 {code} {code} WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] {code} When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4609) Core threads in EnhancedQueueExecutor might timeout below core pool size even if allowCoreTimeOut is false

by Miroslav Novak (Jira)

Miroslav Novak created WFCORE-4609: -------------------------------------- Summary: Core threads in EnhancedQueueExecutor might timeout below core pool size even if allowCoreTimeOut is false Key: WFCORE-4609 URL: https://issues.jboss.org/browse/WFCORE-4609 Project: WildFly Core Issue Type: Bug Components: IO Affects Versions: 10.0.0.Beta2 Reporter: Miroslav Novak Assignee: Flavia Rainone I can see unexpected behavior in EnhancedQueueExecutor [1]. Even when I set allowsCoreThreadTimeOut to false, sometimes happens that pool size goes below core size by a few threads. Test scenario: - create EnhancedQueueExecutor with coreSize=3, maxSize=6, allowsCoreThreadTimeOut=false, keepAliveTimeout=1000ms - submit 6 threads into executor and wait until all are running so maxSize is reached - allow all threads to finish and wait some time for threads to timeout Expected result is that poolSize will be 3 as coreSize=3 but sometimes happens that poolSize is 2 or 1. This might not be a bug as EnhancedQueueExecutor estimates its pool size and might allow to timeout more threads than coreSize. I'm creating this jira so it's explained for future reference. [1] https://github.com/jbossas/jboss-threads/blob/2.3.3.Final/src/main/java/o... [2] https://issues.jboss.org/browse/EAP7-488 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4433) Add the ability to move constraints within patterns in the same way we can move patterns within rules to Guided Rules and Guided Rule Templates

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4433?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4433: -------------------------------- Description: h2. Acceptance test - Guided Rule, move constrain (/) - Guided Rule Template, move constraint (/) - Guided Decision table, BRL Constraint, move constraint (/) - Move, Save and Reopen (/) - Move and Check Source (/) was: h2. Acceptance test - Guided Rule, move constrain - Guided Rule Template, move constraint - Guided Decision table, BRL Constraint, move constraint - Move, Save and Reopen - Move and Check Source > Add the ability to move constraints within patterns in the same way we can move patterns within rules to Guided Rules and Guided Rule Templates > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4433 > URL: https://issues.jboss.org/browse/DROOLS-4433 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: move-up.webm > > > h2. Acceptance test > - Guided Rule, move constrain (/) > - Guided Rule Template, move constraint (/) > - Guided Decision table, BRL Constraint, move constraint (/) > - Move, Save and Reopen (/) > - Move and Check Source (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12091) galleon-pack incorrect processing of subsystem.jaxrs

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-12091?page=com.atlassian.jira.plugin... ] Marek Kopecky updated WFLY-12091: --------------------------------- Component/s: REST > galleon-pack incorrect processing of subsystem.jaxrs > ---------------------------------------------------- > > Key: WFLY-12091 > URL: https://issues.jboss.org/browse/WFLY-12091 > Project: WildFly > Issue Type: Bug > Components: Build System, REST > Affects Versions: 17.0.0.Beta1 > Environment: Fedora > jdk-10 || JDK-8 > mvn 3.3.9 > wfly 17.0.0.Beta1-SNAPSHOT > Reporter: r searls > Assignee: Brian Stansberry > Priority: Blocker > Attachments: xgalleon-pack-issue-may17.zip > > > The tools are not properly handling a simple attribute addition to subsystem.jaxrs. > I have added an attribute to jaxrs/src/main/resources/subsystem-templates/jaxrs.xml. > The new definition is this, > <subsystem xmlns="urn:jboss:domain:jaxrs:2.0" statistics-enabled="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-enabled:false}}" /> > The old definition was this > <subsystem xmlns="urn:jboss:domain:jaxrs:2.0"/> > I have made the following changes in 2 files galleon-pack files but > none of this is reflected in the generated standalone*.xml files. > - to galleon-pack/src/main/resources/feature_groups/basic-profile.xml I added > <feature spec="subsystem.jaxrs"> > <param name="statistics-enabled" value="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-jaxrs:false}}"/> > </feature> > - to galleon-pack/src/main/resources/layers/standalone/jaxrs/layer-spec.xml I added > <feature spec="subsystem.jaxrs"> > <param name="statistics-enabled" value="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-jaxrs:false}}"/> > </feature> > This change is required for https://issues.jboss.org/browse/WFLY-11943 > Attached zip file contains the files I changed and tested with. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4433) Add the ability to move constraints within patterns in the same way we can move patterns within rules to Guided Rules and Guided Rule Templates

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4433?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4433: -------------------------------- Attachment: move-up.webm > Add the ability to move constraints within patterns in the same way we can move patterns within rules to Guided Rules and Guided Rule Templates > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4433 > URL: https://issues.jboss.org/browse/DROOLS-4433 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: move-up.webm > > > h2. Acceptance test > - Guided Rule, move constrain > - Guided Rule Template, move constraint > - Guided Decision table, BRL Constraint, move constraint > - Move, Save and Reopen > - Move and Check Source -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12091) galleon-pack incorrect processing of subsystem.jaxrs

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-12091?page=com.atlassian.jira.plugin... ] Marek Kopecky updated WFLY-12091: --------------------------------- Priority: Blocker (was: Major) > galleon-pack incorrect processing of subsystem.jaxrs > ---------------------------------------------------- > > Key: WFLY-12091 > URL: https://issues.jboss.org/browse/WFLY-12091 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 17.0.0.Beta1 > Environment: Fedora > jdk-10 || JDK-8 > mvn 3.3.9 > wfly 17.0.0.Beta1-SNAPSHOT > Reporter: r searls > Assignee: Brian Stansberry > Priority: Blocker > Attachments: xgalleon-pack-issue-may17.zip > > > The tools are not properly handling a simple attribute addition to subsystem.jaxrs. > I have added an attribute to jaxrs/src/main/resources/subsystem-templates/jaxrs.xml. > The new definition is this, > <subsystem xmlns="urn:jboss:domain:jaxrs:2.0" statistics-enabled="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-enabled:false}}" /> > The old definition was this > <subsystem xmlns="urn:jboss:domain:jaxrs:2.0"/> > I have made the following changes in 2 files galleon-pack files but > none of this is reflected in the generated standalone*.xml files. > - to galleon-pack/src/main/resources/feature_groups/basic-profile.xml I added > <feature spec="subsystem.jaxrs"> > <param name="statistics-enabled" value="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-jaxrs:false}}"/> > </feature> > - to galleon-pack/src/main/resources/layers/standalone/jaxrs/layer-spec.xml I added > <feature spec="subsystem.jaxrs"> > <param name="statistics-enabled" value="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-jaxrs:false}}"/> > </feature> > This change is required for https://issues.jboss.org/browse/WFLY-11943 > Attached zip file contains the files I changed and tested with. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4433) Add the ability to move constraints within patterns in the same way we can move patterns within rules to Guided Rules and Guided Rule Templates

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4433?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4433: -------------------------------- Description: h2. Acceptance test - Guided Rule, move constrain - Guided Rule Template, move constraint - Guided Decision table, BRL Constraint, move constraint - Move, Save and Reopen - Move and Check Source > Add the ability to move constraints within patterns in the same way we can move patterns within rules to Guided Rules and Guided Rule Templates > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4433 > URL: https://issues.jboss.org/browse/DROOLS-4433 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > h2. Acceptance test > - Guided Rule, move constrain > - Guided Rule Template, move constraint > - Guided Decision table, BRL Constraint, move constraint > - Move, Save and Reopen > - Move and Check Source -- 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 August 2019