[jboss-jira] [JBoss JIRA] (WFCORE-340) A write-config operation
Brian Stansberry (JIRA)
issues at jboss.org
Mon Dec 1 15:52:53 EST 2014
[ https://issues.jboss.org/browse/WFCORE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved WFLY-1122 to WFCORE-340:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-340 (was: WFLY-1122)
Component/s: Domain Management
(was: Domain Management)
> A write-config operation
> ------------------------
>
> Key: WFCORE-340
> URL: https://issues.jboss.org/browse/WFCORE-340
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
>
> Operation to force the server to write its config file, without making any actual config change.
> One use case mentioned was to get the config file updated to the latest xml namespaces following an upgrade.
> This should be trivial to implement with an operation step handler that simply does
> context.readResourceForUpdate(PathAddress.EMPT_ADDRESS);
> context.stepCompleted();
> That handler would be registered on:
> 1) The root resource for a non-managed-domain server (for standalone.xml).
> 2) The host=* resource on any HostController (for host.xml).
> 3) The root resource on a HostController that is the master (for domain.xml).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
More information about the jboss-jira
mailing list