September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4477) [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4477?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4477: -------------------------------- Description: When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) h3. Manual acceptance test - Edges crossing ds (/) - Edges outgoing from ds (/) - Edges incoming to ds (/) was: When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) h3. Manual acceptance test - Edges crossing ds - Edges outgoing from ds - Edges incoming to ds > [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4477 > URL: https://issues.jboss.org/browse/DROOLS-4477 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. > DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) > h3. Manual acceptance test > - Edges crossing ds (/) > - Edges outgoing from ds (/) > - Edges incoming to ds (/) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4477) [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4477?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4477: -------------------------------- Description: When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) h3. Manual acceptance test - Edges crossing ds - Edges outgoing from ds - Edges incoming to ds was: When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) > [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4477 > URL: https://issues.jboss.org/browse/DROOLS-4477 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. > DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) > h3. Manual acceptance test > - Edges crossing ds > - Edges outgoing from ds > - Edges incoming to ds -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-167) EAP Operator handling ConfigMap internally

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-167?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-167: ------------------------------------ I have created JBEAP-17559 to track documenting "standalone.xml via ConfigMap" is technical preview feature. > EAP Operator handling ConfigMap internally > ------------------------------------------ > > Key: WFWIP-167 > URL: https://issues.jboss.org/browse/WFWIP-167 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > If I understand description in [1] correctly. To specify custom standalone.xml I have to create ConfigMap with standalone.xml first and afterwards link operator to this ConfigMap. > Is it possible to handle creation of ConfigMap and storing standalone.xml for me? Ideally I just specify file URI where custom standalone.xml is located. This location have to be accessible from operator pod. In this way we can look at it as hiding internals (implementation details) from users. > Currently when user wants to change standalone.xml he does in ConfigMap, not operator. When changing standalone.xml through config map, I assume pod have to be restarted manually. Operator could do that for me. > However this can be triggered by storing newer version of standalone.xml under another key, eg `standalone.xml.v2` and changing `StandaloneConfigMapSpec.key` in operator. > What do you think? Have you considered this approach? > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sta... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12304) Upgrade Apache Artemis from 2.9.0 to 2.10.0

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12304?page=com.atlassian.jira.plugin... ] Flavia Rainone commented on WFLY-12304: --------------------------------------- Jira for netty-xnio-transport upgrade: WFLY-12525 > Upgrade Apache Artemis from 2.9.0 to 2.10.0 > ------------------------------------------- > > Key: WFLY-12304 > URL: https://issues.jboss.org/browse/WFLY-12304 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Martin Stefanko > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: blocker-WF18, downstream_dependency > > Upgrade Apache Artemis from 2.9.0.Final to 2.10.0.Final. > Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12525) Upgrade netty-xnio-transport to 0.1.7.Final

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12525?page=com.atlassian.jira.plugin... ] Flavia Rainone moved WFCORE-4655 to WFLY-12525: ----------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-12525 (was: WFCORE-4655) > Upgrade netty-xnio-transport to 0.1.7.Final > ------------------------------------------- > > Key: WFLY-12525 > URL: https://issues.jboss.org/browse/WFLY-12525 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Blocker > > Upgrade the netty-xnio-transport containing fix for: [XNIO#14|https://github.com/xnio/netty-xnio-transport/issues/14] -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4655) Upgrade netty-xnio-transport to 0.1.7.Final

by Flavia Rainone (Jira)

Flavia Rainone created WFCORE-4655: -------------------------------------- Summary: Upgrade netty-xnio-transport to 0.1.7.Final Key: WFCORE-4655 URL: https://issues.jboss.org/browse/WFCORE-4655 Project: WildFly Core Issue Type: Component Upgrade Reporter: Flavia Rainone Assignee: Flavia Rainone Upgrade the netty-xnio-transport containing fix for: [XNIO#14|https://github.com/xnio/netty-xnio-transport/issues/14] -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD

by Martin Choma (Jira)

Martin Choma created WFWIP-192: ---------------------------------- Summary: Sync eap CRD with wildfly CRD Key: WFWIP-192 URL: https://issues.jboss.org/browse/WFWIP-192 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Choma Assignee: Brian Stansberry Comparing wildfly and eap CRD revealed differences {code} wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd diff wildfly_operator_crd eap_operator_crd {code} {code} 36,37d35 < disableHTTPRoute: < type: boolean 50,53d47 < sessionAffinity: < description: SessionAffinity defines if connections from the same client < ip are passed to the same WildFlyServer instance/pod each time < type: boolean 79,82d72 < hosts: < items: < type: string < type: array 94a85,86 > required: > - pods {code} Please sync so we can test against. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ] Martin Choma reassigned WFWIP-192: ---------------------------------- Assignee: Jeff Mesnil (was: Brian Stansberry) > Sync eap CRD with wildfly CRD > ----------------------------- > > Key: WFWIP-192 > URL: https://issues.jboss.org/browse/WFWIP-192 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > Comparing wildfly and eap CRD revealed differences > {code} > wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd > wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd > diff wildfly_operator_crd eap_operator_crd > {code} > {code} > 36,37d35 > < disableHTTPRoute: > < type: boolean > 50,53d47 > < sessionAffinity: > < description: SessionAffinity defines if connections from the same client > < ip are passed to the same WildFlyServer instance/pod each time > < type: boolean > 79,82d72 > < hosts: > < items: > < type: string > < type: array > 94a85,86 > > required: > > - pods > {code} > Please sync so we can test against. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-948) install-ocp4 jenkins job is failing because of full provider_net_shared_2 network

by Filip Brychta (Jira)

Filip Brychta created SWSQE-948: ----------------------------------- Summary: install-ocp4 jenkins job is failing because of full provider_net_shared_2 network Key: SWSQE-948 URL: https://issues.jboss.org/browse/SWSQE-948 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12304) Upgrade Apache Artemis from 2.9.0 to 2.10.0

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12304?page=com.atlassian.jira.plugin... ] Flavia Rainone commented on WFLY-12304: --------------------------------------- The problem is fixed here: https://github.com/xnio/netty-xnio-transport/pull/15 I'll do a release after running a few more tests locally. > Upgrade Apache Artemis from 2.9.0 to 2.10.0 > ------------------------------------------- > > Key: WFLY-12304 > URL: https://issues.jboss.org/browse/WFLY-12304 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Martin Stefanko > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: blocker-WF18, downstream_dependency > > Upgrade Apache Artemis from 2.9.0.Final to 2.10.0.Final. > Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 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 September 2019