March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6803) Add multi-server support to mod_cluster

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6803?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-6803: -------------------------------------- This is a new feature, so it will need to go through the EAP7 process. > Add multi-server support to mod_cluster > --------------------------------------- > > Key: WFLY-6803 > URL: https://issues.jboss.org/browse/WFLY-6803 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). > mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-8449: ------------------------------------ Assignee: Stuart Douglas (was: Fedor Gavrilov) > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Stuart Douglas > Labels: downstream_dependency, ejb > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10113) EJB contextData not sent back to client in response

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-10113: ------------------------------------- Summary: EJB contextData not sent back to client in response Key: WFLY-10113 URL: https://issues.jboss.org/browse/WFLY-10113 Project: WildFly Issue Type: Feature Request Components: EJB Reporter: Fedor Gavrilov Assignee: Fedor Gavrilov With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. Since AS7 and WildFly the only possibility is to pass such context from the client to the server. It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-8449: --------------------------------- Issue Type: Feature Request (was: Bug) > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: downstream_dependency, ejb > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10004) Removing modules moved into wildfly-core for wildfly-url-http integration

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10004?page=com.atlassian.jira.plugin... ] Stuart Douglas reopened WFLY-10004: ----------------------------------- > Removing modules moved into wildfly-core for wildfly-url-http integration > ------------------------------------------------------------------------- > > Key: WFLY-10004 > URL: https://issues.jboss.org/browse/WFLY-10004 > Project: WildFly > Issue Type: Task > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 13.0.0.Beta1 > > > As part of WFCORE-3658 was some modules like httpclient moved into wildfly-core. > This issue is for referencing from PR removing them from wildfly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10004) Removing modules moved into wildfly-core for wildfly-url-http integration

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10004?page=com.atlassian.jira.plugin... ] Stuart Douglas resolved WFLY-10004. ----------------------------------- Resolution: Rejected > Removing modules moved into wildfly-core for wildfly-url-http integration > ------------------------------------------------------------------------- > > Key: WFLY-10004 > URL: https://issues.jboss.org/browse/WFLY-10004 > Project: WildFly > Issue Type: Task > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 13.0.0.Beta1 > > > As part of WFCORE-3658 was some modules like httpclient moved into wildfly-core. > This issue is for referencing from PR removing them from wildfly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10112) Upgrade Hibernate Validator to 6.0.9.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10112?page=com.atlassian.jira.plugin... ] Stuart Douglas resolved WFLY-10112. ----------------------------------- Resolution: Done > Upgrade Hibernate Validator to 6.0.9.Final > ------------------------------------------ > > Key: WFLY-10112 > URL: https://issues.jboss.org/browse/WFLY-10112 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Guillaume Smet > Assignee: Guillaume Smet > Fix For: 13.0.0.Beta1 > > > No migration concerns from 6.0.7.Final to 6.0.9.Final. > The important point is that a regression from 5.x to 6.0.x was fixed in this release: https://hibernate.atlassian.net/browse/HV-1596 . > We also reduced the memory allocation rate in some common use cases. > Full changelog of 6.0.8.Final: > https://hibernate.atlassian.net/projects/HV/versions/31620/tab/release-re... > Full changelog of 6.0.9.Final: > https://hibernate.atlassian.net/projects/HV/versions/31646/tab/release-re... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10066) JACC is broken after server reload

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10066?page=com.atlassian.jira.plugin... ] Stuart Douglas reassigned WFLY-10066: ------------------------------------- Assignee: Stuart Douglas (was: Darran Lofthouse) > JACC is broken after server reload > ---------------------------------- > > Key: WFLY-10066 > URL: https://issues.jboss.org/browse/WFLY-10066 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 13.0.0.Beta1 > > > It was discovered by https://github.com/wildfly/wildfly/pull/10829 that JACC has problems after server reload. > org.jboss.security.jacc.JBossPolicyConfigurationFactory will always use the first 'org.jboss.security.jacc.DelegatingPolicy' that is set, while on reload org.jboss.as.security.service.SecurityBootstrapService will create and install a new policy, which means that after you execute a reload operation JACC is broken (provided the JBossPolicyConfigurationFactory was initialised before the reload). > This will need to be fixed somehow, either by using the same DelegatingPolicy after reload, or by clearing the state in JBossPolicyConfigurationFactory. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2430) [DMN Editor] Decision Navigator dock (DRD View)

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2430?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2430: --------------------------------------- Description: Add the DRD tree to the Decision Navigator dock. !prototype.png|thumbnail! See more details [here|https://docs.google.com/document/d/14pnw6QUTj5BsUJyz4uP_ozLLkYBvCYGX...] > [DMN Editor] Decision Navigator dock (DRD View) > ----------------------------------------------- > > Key: DROOLS-2430 > URL: https://issues.jboss.org/browse/DROOLS-2430 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Minor > Attachments: prototype.png > > > Add the DRD tree to the Decision Navigator dock. > !prototype.png|thumbnail! > See more details [here|https://docs.google.com/document/d/14pnw6QUTj5BsUJyz4uP_ozLLkYBvCYGX...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2430) [DMN Editor] Decision Navigator dock (DRD View)

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2430?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2430: --------------------------------------- Description: Add the DRD tree to the Decision Navigator dock. !prototype.png|thumbnail! See more details [here|https://docs.google.com/document/d/14pnw6QUTj5BsUJyz4uP_ozLLkYBvCYGX...]. was: Add the DRD tree to the Decision Navigator dock. !prototype.png|thumbnail! See more details [here|https://docs.google.com/document/d/14pnw6QUTj5BsUJyz4uP_ozLLkYBvCYGX...] > [DMN Editor] Decision Navigator dock (DRD View) > ----------------------------------------------- > > Key: DROOLS-2430 > URL: https://issues.jboss.org/browse/DROOLS-2430 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Minor > Attachments: prototype.png > > > Add the DRD tree to the Decision Navigator dock. > !prototype.png|thumbnail! > See more details [here|https://docs.google.com/document/d/14pnw6QUTj5BsUJyz4uP_ozLLkYBvCYGX...]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 March 2018