June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10596) Document missing undertow capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10596?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10596: --------------------------------------- e.g. https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/u... is missing > Document missing undertow capabilities > -------------------------------------- > > Key: WFLY-10596 > URL: https://issues.jboss.org/browse/WFLY-10596 > Project: WildFly > Issue Type: Sub-task > Components: Web (Undertow) > Reporter: Jeff Mesnil > Assignee: Stuart Douglas > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10596) Document missing undertow capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10596?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-10596: ------------------------------------- Assignee: Flavia Rainone (was: Stuart Douglas) Fixing assignee. > Document missing undertow capabilities > -------------------------------------- > > Key: WFLY-10596 > URL: https://issues.jboss.org/browse/WFLY-10596 > Project: WildFly > Issue Type: Sub-task > Components: Web (Undertow) > Reporter: Jeff Mesnil > Assignee: Flavia Rainone > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12224) CLI output is doubled after embed-server reload

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-12224: ----------------------------------- Summary: CLI output is doubled after embed-server reload Key: WFLY-12224 URL: https://issues.jboss.org/browse/WFLY-12224 Project: WildFly Issue Type: Bug Components: CLI Affects Versions: 18.0.0.Beta1 Reporter: Ondrej Kotek Assignee: Jean Francois Denise CLI output is doubled after embed-server reload: {noformat} [okotek@localhost wildfly-18.0.0.Beta1-SNAPSHOT]$ ./bin/jboss-cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] embed-server [standalone@embedded /] :whoami { "outcome" => "success", "result" => {"identity" => {"username" => "anonymous"}} } [standalone@embedded /] reload [standalone@embedded /] :whoami 12:34:27,735 INFO [org.jboss.as.cli.CommandContext] (CLI command) { "outcome" => "success", "result" => {"identity" => {"username" => "anonymous"}} } { "outcome" => "success", "result" => {"identity" => {"username" => "anonymous"}} } {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4203) Test Scenario: use ExtendedDMNProfile for FEEL expressions

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4203?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4203: ---------------------------------- Sprint: 2019 Week 23-25 > Test Scenario: use ExtendedDMNProfile for FEEL expressions > ---------------------------------------------------------- > > Key: DROOLS-4203 > URL: https://issues.jboss.org/browse/DROOLS-4203 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > FEEL interpreter by default doesn't accept DMN 1.2 functions. Use ExtendedDMNProfile for FEEL to enable the support -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4203) Test Scenario: use ExtendedDMNProfile for FEEL expressions

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4203?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4203: ---------------------------------- Story Points: 1 > Test Scenario: use ExtendedDMNProfile for FEEL expressions > ---------------------------------------------------------- > > Key: DROOLS-4203 > URL: https://issues.jboss.org/browse/DROOLS-4203 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > FEEL interpreter by default doesn't accept DMN 1.2 functions. Use ExtendedDMNProfile for FEEL to enable the support -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12222) Clustering subsystems integration with WildFly Discovery SPI (tracker Jira)

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12222?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12222: ---------------------------------- Description: Ultimately, we could employ WildFly Discovery SPI to handle services discovery in a generic way. However, since the subsystem currently only supplies one provider based on static discovery, its usefulness is limited. To untangle the chicken-egg problem, we could first integrate the clustering subsystems with the discovery SPI, # JGroups discovery # remote-cache-container remote servers # mod_cluster then supply discovery providers, # static list (implemented) # multicast-based # k8s-based (replacing JGroups' OPENSHIFT_PING, DNS_PING, KUBE_PING, etc) # cloud providers specific (replacing S3_PING, NATIVE_S3_PING, AZURE_PING, GOOGLE_PING, etc) This requires fixes to the discovery subsystem such as # ability to register new providers # changing static providers should require server reload # etc was:Ultimately, > Clustering subsystems integration with WildFly Discovery SPI (tracker Jira) > --------------------------------------------------------------------------- > > Key: WFLY-12222 > URL: https://issues.jboss.org/browse/WFLY-12222 > Project: WildFly > Issue Type: Task > Components: Clustering, mod_cluster > Affects Versions: 17.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Ultimately, we could employ WildFly Discovery SPI to handle services discovery in a generic way. However, since the subsystem currently only supplies one provider based on static discovery, its usefulness is limited. To untangle the chicken-egg problem, we could first integrate the clustering subsystems with the discovery SPI, > # JGroups discovery > # remote-cache-container remote servers > # mod_cluster > then supply discovery providers, > # static list (implemented) > # multicast-based > # k8s-based (replacing JGroups' OPENSHIFT_PING, DNS_PING, KUBE_PING, etc) > # cloud providers specific (replacing S3_PING, NATIVE_S3_PING, AZURE_PING, GOOGLE_PING, etc) > This requires fixes to the discovery subsystem such as > # ability to register new providers > # changing static providers should require server reload > # etc -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12222) Clustering subsystems integration with WildFly Discovery SPI (tracker Jira)

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12222?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12222: ---------------------------------- Description: Ultimately, we could employ WildFly Discovery SPI to handle services discovery in a generic way. However, since the subsystem currently only supplies one provider based on static discovery, its usefulness is limited. To untangle the chicken-egg problem, we could first integrate the clustering subsystems with the discovery SPI, * JGroups discovery * remote-cache-container remote servers * mod_cluster then supply discovery providers, * static list (implemented) * multicast-based * k8s-based (replacing JGroups' OPENSHIFT_PING, DNS_PING, KUBE_PING, etc) * cloud providers specific (replacing S3_PING, NATIVE_S3_PING, AZURE_PING, GOOGLE_PING, etc) This requires fixes to the discovery subsystem such as * ability to register new providers * changing static providers should require server reload * TBD was: Ultimately, we could employ WildFly Discovery SPI to handle services discovery in a generic way. However, since the subsystem currently only supplies one provider based on static discovery, its usefulness is limited. To untangle the chicken-egg problem, we could first integrate the clustering subsystems with the discovery SPI, # JGroups discovery # remote-cache-container remote servers # mod_cluster then supply discovery providers, # static list (implemented) # multicast-based # k8s-based (replacing JGroups' OPENSHIFT_PING, DNS_PING, KUBE_PING, etc) # cloud providers specific (replacing S3_PING, NATIVE_S3_PING, AZURE_PING, GOOGLE_PING, etc) This requires fixes to the discovery subsystem such as # ability to register new providers # changing static providers should require server reload # etc > Clustering subsystems integration with WildFly Discovery SPI (tracker Jira) > --------------------------------------------------------------------------- > > Key: WFLY-12222 > URL: https://issues.jboss.org/browse/WFLY-12222 > Project: WildFly > Issue Type: Task > Components: Clustering, mod_cluster > Affects Versions: 17.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Ultimately, we could employ WildFly Discovery SPI to handle services discovery in a generic way. However, since the subsystem currently only supplies one provider based on static discovery, its usefulness is limited. To untangle the chicken-egg problem, we could first integrate the clustering subsystems with the discovery SPI, > * JGroups discovery > * remote-cache-container remote servers > * mod_cluster > then supply discovery providers, > * static list (implemented) > * multicast-based > * k8s-based (replacing JGroups' OPENSHIFT_PING, DNS_PING, KUBE_PING, etc) > * cloud providers specific (replacing S3_PING, NATIVE_S3_PING, AZURE_PING, GOOGLE_PING, etc) > This requires fixes to the discovery subsystem such as > * ability to register new providers > * changing static providers should require server reload > * TBD -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12222) Clustering subsystems integration with WildFly Discovery SPI (tracker Jira)

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12222?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12222: ---------------------------------- Description: Ultimately, > Clustering subsystems integration with WildFly Discovery SPI (tracker Jira) > --------------------------------------------------------------------------- > > Key: WFLY-12222 > URL: https://issues.jboss.org/browse/WFLY-12222 > Project: WildFly > Issue Type: Task > Components: Clustering, mod_cluster > Affects Versions: 17.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Ultimately, -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12223) Configuring remote-cache-container datagrid nodes based on WildFly Discovery SPI

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12223: ------------------------------------- Summary: Configuring remote-cache-container datagrid nodes based on WildFly Discovery SPI Key: WFLY-12223 URL: https://issues.jboss.org/browse/WFLY-12223 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 17.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12222) Clustering subsystems integration with WildFly Discovery SPI (tracker Jira)

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12222?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12222: ---------------------------------- Component/s: mod_cluster > Clustering subsystems integration with WildFly Discovery SPI (tracker Jira) > --------------------------------------------------------------------------- > > Key: WFLY-12222 > URL: https://issues.jboss.org/browse/WFLY-12222 > Project: WildFly > Issue Type: Task > Components: Clustering, mod_cluster > Affects Versions: 17.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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