December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-367) Move ClientConfigurationImpl factory methods into ModelControllerClientConfiguration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-367?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-367: --------------------------------------- Assignee: Emmanuel Hugonnet > Move ClientConfigurationImpl factory methods into ModelControllerClientConfiguration > ------------------------------------------------------------------------------------ > > Key: WFCORE-367 > URL: https://issues.jboss.org/browse/WFCORE-367 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 1.0.0.Beta1 > > > ClientConfigurationImpl includes a bunch of static factory methods that would fit better in a Factory class in the ModelControllerClientConfiguration interface. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-361) CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-361?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-361: --------------------------------------- Assignee: Emmanuel Hugonnet (was: Brian Stansberry) Emmanuel, once WFCORE-400 is resolved, please just resolve this one as Out of Date. > CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error) > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-361 > URL: https://issues.jboss.org/browse/WFCORE-361 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Pavel Janousek > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as: > {code} > <server xmlns="urn:jboss:domain:1.3"> > {code} > The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd. > The very common Linux system has implemented and enabled dualstack in these days. If we instruct AS instance to bind to +any+ IPv4 address via {code}<interface name="public"> > <any-ipv4-address /> > </interface>{code} > The real result is to bind running AS instance to +any+ IP address, not only in IPv4 address space but in IPv6 too! > With default setting (= -Djava.net.preferIPv4Stack=true), result is correct - it is bound to ANY IPv4 addresses only. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-400) Remove <any-ipv4-address/> and <any-ipv6-address>

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-400?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-400: --------------------------------------- Assignee: Emmanuel Hugonnet > Remove <any-ipv4-address/> and <any-ipv6-address> > ------------------------------------------------- > > Key: WFCORE-400 > URL: https://issues.jboss.org/browse/WFCORE-400 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > These options have no reliable semantic (see, for example, WFLY-533) and should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-309) system properties are trim()'d and loose whitespace

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-309?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-309: --------------------------------------- Assignee: Emmanuel Hugonnet (was: Brian Stansberry) > system properties are trim()'d and loose whitespace > --------------------------------------------------- > > Key: WFCORE-309 > URL: https://issues.jboss.org/browse/WFCORE-309 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Tom Fonteyne > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > When a system property was defined as: > /system-property=foo:add(value=" spaces "); > it gets written with the correct spaces around it to the configuration file. > When the configuration is read the value gets trimmed and the prefix/suffix of spaces is lost. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-382) Support for profile and socket binding group includes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-382?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-382: --------------------------------------- Assignee: Kabir Khan > Support for profile and socket binding group includes > ----------------------------------------------------- > > Key: WFCORE-382 > URL: https://issues.jboss.org/browse/WFCORE-382 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 1.0.0.Beta1 > > > Restore the ability to have a profile include another profile and for a socket-binding-group to include another socket-binding-group. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-419) Expose client socket binding config through CLI connect configs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-419?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-419: --------------------------------------- Assignee: Emmanuel Hugonnet (was: Alexey Loubyansky) Alexey, I've assigned Emmanuel to WFCORE-371, so it seems sensible to have him handle this aspect as well. > Expose client socket binding config through CLI connect configs > --------------------------------------------------------------- > > Key: WFCORE-419 > URL: https://issues.jboss.org/browse/WFCORE-419 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > Once AS7-6277 is done, continue exposing the client bind socket config to CLI users. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-239) Socket binding remove does not respect allow-resource-service-restart

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-239?page=com.atlassian.jira.plugin... ] Stuart Douglas reassigned WFCORE-239: ------------------------------------- Assignee: Stuart Douglas (was: Emmanuel Hugonnet) > Socket binding remove does not respect allow-resource-service-restart > --------------------------------------------------------------------- > > Key: WFCORE-239 > URL: https://issues.jboss.org/browse/WFCORE-239 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-371) Expose mgmt client socket binding config through ModelControllerClient Factory

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-371?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-371: --------------------------------------- Assignee: Emmanuel Hugonnet > Expose mgmt client socket binding config through ModelControllerClient Factory > ------------------------------------------------------------------------------ > > Key: WFCORE-371 > URL: https://issues.jboss.org/browse/WFCORE-371 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > Parent task used a secret system property to configure this to support Open Shift's immediate need, but proper configuration is needed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-293) Add EAP 6.2 and 6.3 to versions tested in core-model-test

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-293?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-293: --------------------------------------- Assignee: Emmanuel Hugonnet Emmanuel, I have no idea if this issue is still valid. > Add EAP 6.2 and 6.3 to versions tested in core-model-test > --------------------------------------------------------- > > Key: WFCORE-293 > URL: https://issues.jboss.org/browse/WFCORE-293 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Priority: Blocker > Fix For: 1.0.0.Beta1 > > > The latest EAP versions are not being tested in core-model-test. > Seems there are problems with 6.2: > https://github.com/wildfly/wildfly/pull/6409 > I haven't tried 6.3 because it is not complete. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-193) Moveorg.jboss.as.test.smoke.mgmt.servermodule tests from full to core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-193?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-193: --------------------------------------- Assignee: Emmanuel Hugonnet > Moveorg.jboss.as.test.smoke.mgmt.servermodule tests from full to core > --------------------------------------------------------------------- > > Key: WFCORE-193 > URL: https://issues.jboss.org/browse/WFCORE-193 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > The tests in org.jboss.as.test.smoke.mgmt.servermodule belong in core, not full. > Don't just move the package; integrate the tests into appropriate spots in the existing testsuite-core/standalone packages. > Adapt the ones that use sar deployments to use org.jboss.as.test.deployment.trivial instead, as we plan to move sar support out of core. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 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 December 2014