December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-336) Ability for Deployment Overlays to overlay System Properties

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-336?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-2720 to WFCORE-336: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-336 (was: WFLY-2720) Component/s: Domain Management (was: Domain Management) > Ability for Deployment Overlays to overlay System Properties > ------------------------------------------------------------ > > Key: WFCORE-336 > URL: https://issues.jboss.org/browse/WFCORE-336 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Joshua Henn > > Currently Deployment Overlays allow only the replacing whole resource files. It would be nice to also be able to overlay System Properties that take precedent over globally defined properties. > ie. > {code:xml} > <deployment-overlays> > <deployment-overlay name="myOverlay"> > <system-properties> > <property name="datasource" value="java:jboss/datasources/controller"/> > </system-properties> > <deployment name="controller.war"/> > </deployment-overlay> > </deployment-overlays> > {code} > Usecase: > Have two deployments active of the same application, run-time configured by descriptor replacements via System Properties. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-337) Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-337?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1112 to WFCORE-337: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-337 (was: WFLY-1112) Component/s: Domain Management (was: Domain Management) > Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-337 > URL: https://issues.jboss.org/browse/WFCORE-337 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > Users should be able to read the xsd to tell if expressions are supported for a given attribute/element. Reading the management API metadata is too cumbersome and indirect. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master based on a shared lock

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1429 to WFCORE-338: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-338 (was: WFLY-1429) Component/s: Domain Management (was: Domain Management) > Auto-promotion of slave HC to master based on a shared lock > ----------------------------------------------------------- > > Key: WFCORE-338 > URL: https://issues.jboss.org/browse/WFCORE-338 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > > Implement an option for a properly configured slave HC to promote itself to master after acquiring an exclusive lock mediated via some persistent store shared between all HCs that are possibly master. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-330) No Spaces Allowed in Host -> Name, but ' do work, odd

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-330?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1050 to WFCORE-330: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-330 (was: WFLY-1050) Component/s: Domain Management (was: Domain Management) > No Spaces Allowed in Host -> Name, but ' do work, odd > ----------------------------------------------------- > > Key: WFCORE-330 > URL: https://issues.jboss.org/browse/WFCORE-330 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Jim Tyrrell > Labels: eap6-ux > > For some reason spaces do not seem to be allowed, but an Apostrophe seems to be okay. > [Host Controller] 20:56:20,250 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.IllegalArgumentException: JBAS014719: Invalid value specification Jim's Most_Excellent_Domain_Ever_so_here > Would be nice if the error message would kick out what values are acceptable? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-331) Configurable location for deployment scanner marker files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-331?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-2503 to WFCORE-331: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-331 (was: WFLY-2503) Component/s: Domain Management (was: Domain Management) > Configurable location for deployment scanner marker files > --------------------------------------------------------- > > Key: WFCORE-331 > URL: https://issues.jboss.org/browse/WFCORE-331 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > Add marker-dir and marker-dir-relative-to attributes to the deployment scanner resource. These control where the marker files are written, with the default being the dir being scanned itself. > The idea here is to allow sharing of a deployments/ dir by letting users redirect the markers to some other location. > To store in a server-specific subdir of deployments (making the markers still fairly accessible the user): > {code} > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" > marker-dir="deployments/${jboss.node.name}" > marker-dir-relative-to="jboss.server.base.dir" > /> > {code} > To store the markers in the data dir, out of sight, out of mind: > {code} > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" > marker-dir="deployment-scanner-markers" > marker-dir-relative-to="jboss.server.data.dir" > /> > {code} > This all sounds simple enough, but anyone looking into it *must* assume this will be a highly complex task, as the scanner itself is very complex and assumes that the deployments and the markers are in the same dir. Extremely extensive test coverage will be required. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-332) Allow RestartParentXXXHandlers to handle resources with multiple services

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-332?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1165 to WFCORE-332: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-332 (was: WFLY-1165) Component/s: Domain Management (was: Domain Management) > Allow RestartParentXXXHandlers to handle resources with multiple services > ------------------------------------------------------------------------- > > Key: WFCORE-332 > URL: https://issues.jboss.org/browse/WFCORE-332 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Richard Achmatowicz > Assignee: Jason Greene > Priority: Minor > > I'd like to use RestartParentWriteAttributeHandler to allow handling of attributes which, when updated, case a restart of only the services installed by their parent resource. These are really useful classes and solve a commonly encountered problem. > However, the resource I want to restart involves four services, and it appears that RestartParentWriteAttriubuteHandler assumes that for every parent key name, there is only a single service registered. > If we had the private methods: > ServiceName[] getParentServiceNames(PathAddress address) > boolean areParentServicesInstalled(ServiceName[] names) > void removeServices(OperationContext context, ServiceNames[] names, ModelNode parentModel) > this could be made to work for more general resources. > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-333) Provide a management operation to list the servers in a server group (domain mode)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-333?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1078 to WFCORE-333: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-333 (was: WFLY-1078) Component/s: CLI Domain Management (was: CLI) (was: Domain Management) > Provide a management operation to list the servers in a server group (domain mode) > ---------------------------------------------------------------------------------- > > Key: WFCORE-333 > URL: https://issues.jboss.org/browse/WFCORE-333 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Richard Achmatowicz > Assignee: Alexey Loubyansky > Priority: Minor > > In domain mode, an end user might want to start one or more servers by hand in a named server group. Obtaining the list of servers in a server group is not readily available: the "group" attribute is embedded in server-config, so we have to drill down into every /host=*/server-config=* combination to find out which servers belong to a specific server group. > It would improve the user experience to have an operation which shows which servers are in a given server group. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-334) "Ignore failure" for management operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-334?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1395 to WFCORE-334: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-334 (was: WFLY-1395) Component/s: Domain Management (was: Domain Management) > "Ignore failure" for management operations > ------------------------------------------ > > Key: WFCORE-334 > URL: https://issues.jboss.org/browse/WFCORE-334 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Ondrej Zizka > > Most operations don't follow any "overwrite" concept. > To emulate it, one needs to check for existence of a resource, conditionally delete it, and then create the new one. > This is not easily applicable in a batch. > Implementing overwrite for all actions would be tedious. > But this could help: > Another "standard" property (similar to {{address}} and {{op-name}}) "onFail=ignore" or such, which would make the operation not fail if an exception occurs. A short CLI syntax could be a '?' at the end of operation's name: > {code} > /foo=bar/boo=baz:remove?() > {code} > This would allow mgmt API users to queue a removing operation without knowing if it exists; thus, effectively, doing an overwrite. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-326) Pushing configuration artifacts to domain servers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-326?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1179 to WFCORE-326: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-326 (was: WFLY-1179) Component/s: Domain Management (was: Domain Management) > Pushing configuration artifacts to domain servers > ------------------------------------------------- > > Key: WFCORE-326 > URL: https://issues.jboss.org/browse/WFCORE-326 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darragh Sherwin > Priority: Minor > Labels: clustering, domain > > It should be possible to push configurations artifacts like property files, keystores, etc to domain servers from a domain controller and for applications to reference these configuration artifacts in a generic manner. > Weblogic provides this functionality -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-327) Add file based auth to http management interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-327?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1150 to WFCORE-327: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-327 (was: WFLY-1150) Component/s: Domain Management (was: Domain Management) > Add file based auth to http management interface > ------------------------------------------------ > > Key: WFCORE-327 > URL: https://issues.jboss.org/browse/WFCORE-327 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Max Rydahl Andersen > Assignee: Darran Lofthouse > > usecase: allow clients using http api to use the file based auth so they do not have to rely on the binary protocol and remoting. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

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 December 2014