August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10634) mod_cluster custom metrics are loaded from the subsystem classloader

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10634?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10634: ---------------------------------- Description: The mod_cluster custom load metrics classes are loaded from the subsystem classloader which requires users to tinker with our module structure. This is wrong. We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). was:We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). > mod_cluster custom metrics are loaded from the subsystem classloader > -------------------------------------------------------------------- > > Key: WFLY-10634 > URL: https://issues.jboss.org/browse/WFLY-10634 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The mod_cluster custom load metrics classes are loaded from the subsystem classloader which requires users to tinker with our module structure. This is wrong. > We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10634) mod_cluster custom load metric classes are loaded from the subsystem classloader

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10634?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10634: ---------------------------------- Summary: mod_cluster custom load metric classes are loaded from the subsystem classloader (was: mod_cluster custom metrics are loaded from the subsystem classloader) > mod_cluster custom load metric classes are loaded from the subsystem classloader > -------------------------------------------------------------------------------- > > Key: WFLY-10634 > URL: https://issues.jboss.org/browse/WFLY-10634 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The mod_cluster custom load metrics classes are loaded from the subsystem classloader which requires users to tinker with our module structure. This is wrong. > We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10634) mod_cluster custom metrics are loaded from the subsystem classloader

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10634?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10634: ---------------------------------- Issue Type: Bug (was: Enhancement) > mod_cluster custom metrics are loaded from the subsystem classloader > -------------------------------------------------------------------- > > Key: WFLY-10634 > URL: https://issues.jboss.org/browse/WFLY-10634 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10634) mod_cluster custom metrics are loaded from the subsystem classloader

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10634?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10634: ---------------------------------- Summary: mod_cluster custom metrics are loaded from the subsystem classloader (was: mod_cluster should allow to specify module to load custom metric from) > mod_cluster custom metrics are loaded from the subsystem classloader > -------------------------------------------------------------------- > > Key: WFLY-10634 > URL: https://issues.jboss.org/browse/WFLY-10634 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10489) Rename mod_cluster Tomcat/JBoss-web era "connector" attribute to listener

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10489: ---------------------------------- Summary: Rename mod_cluster Tomcat/JBoss-web era "connector" attribute to listener (was: Rename mod_cluster "connector" attribute to listener) > Rename mod_cluster Tomcat/JBoss-web era "connector" attribute to listener > ------------------------------------------------------------------------- > > Key: WFLY-10489 > URL: https://issues.jboss.org/browse/WFLY-10489 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing. > The goal is to rename this to listener. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10489) Rename mod_cluster Tomcat/JBossWeb-era "connector" attribute to listener

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10489: ---------------------------------- Summary: Rename mod_cluster Tomcat/JBossWeb-era "connector" attribute to listener (was: Rename mod_cluster Tomcat/JBoss-web era "connector" attribute to listener) > Rename mod_cluster Tomcat/JBossWeb-era "connector" attribute to listener > ------------------------------------------------------------------------ > > Key: WFLY-10489 > URL: https://issues.jboss.org/browse/WFLY-10489 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing. > The goal is to rename this to listener. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10489) Rename mod_cluster "connector" attribute to listener

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10489: ---------------------------------- Summary: Rename mod_cluster "connector" attribute to listener (was: mod_cluster listener attribute is still called "connector") > Rename mod_cluster "connector" attribute to listener > ---------------------------------------------------- > > Key: WFLY-10489 > URL: https://issues.jboss.org/browse/WFLY-10489 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing. > The goal is to rename this to listener. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10489) mod_cluster listener attribute is still called "connector"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10489: ---------------------------------- Description: mod_cluster listener attribute name is still "connector" which is confusing. The goal is to rename this to listener. was: mod_cluster listener attribute is still called "connector" which is confusing. The goal is to rename this to listener. > mod_cluster listener attribute is still called "connector" > ---------------------------------------------------------- > > Key: WFLY-10489 > URL: https://issues.jboss.org/browse/WFLY-10489 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > mod_cluster listener attribute name is still "connector" which is confusing. > The goal is to rename this to listener. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10489) mod_cluster listener attribute is still called "connector"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10489: ---------------------------------- Description: mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing. The goal is to rename this to listener. was: mod_cluster listener attribute name is still "connector" which is confusing. The goal is to rename this to listener. > mod_cluster listener attribute is still called "connector" > ---------------------------------------------------------- > > Key: WFLY-10489 > URL: https://issues.jboss.org/browse/WFLY-10489 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing. > The goal is to rename this to listener. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2564) [DMN Designer] Data-types: Grid: General

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2564: -------------------------------- Description: Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. h3. Manual Acceptance test - Create two decision nodes - Specify some expression for both - Open expression editor for first - Rename the decision node in properties panel -- Check *<< Back to XXX* (/) -- Check Expression header cell (x) - Via navigation dock open second node expression -- Check *<< Back to XXX* (/) -- Check Expression header cell (x) - Rename the decision node in properties panel -- Check *<< Back to XXX* (/) -- Check Expression header cell (x) - Save and reopen diagram -- Check names are stored (/) was: Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. h3. Manual Acceptance test - Create two decision nodes - Specify some expression for both - Open expression editor for first - Rename the decision node in properties panel -- Check *<< Back to XXX* - Via navigation dock open second node expression -- Check *<< Back to XXX* - Rename the decision node in properties panel -- Check *<< Back to XXX* - Save and reopen diagram -- Check names are stored > [DMN Designer] Data-types: Grid: General > ---------------------------------------- > > Key: DROOLS-2564 > URL: https://issues.jboss.org/browse/DROOLS-2564 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. > h3. Manual Acceptance test > - Create two decision nodes > - Specify some expression for both > - Open expression editor for first > - Rename the decision node in properties panel > -- Check *<< Back to XXX* (/) > -- Check Expression header cell (x) > - Via navigation dock open second node expression > -- Check *<< Back to XXX* (/) > -- Check Expression header cell (x) > - Rename the decision node in properties panel > -- Check *<< Back to XXX* (/) > -- Check Expression header cell (x) > - Save and reopen diagram > -- Check names are stored (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 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 August 2018