[
https://issues.jboss.org/browse/WFCORE-2070?page=com.atlassian.jira.plugi...
]
Brian Stansberry resolved WFCORE-2070.
--------------------------------------
Resolution: Out of Date
It turns out WFCORE-2070 is invalid. You actually can invoke the kill/destroy ops against
the server resource. They are registered by a call to
ServerConfigResourceDefintion.registerServerLifecycleOperations.
DomainModelControllerService registers that when the server registers with the HC.
The op doesn’t show up in tab completion because the ‘server’ resource is kind of an odd
thing, existing in two places simulaneously — as a resource in the HC and as the root of
the resource tree on the server itself. My guess is operations like read-operation-names
are not dealing with that dual nature correctly.
There are other strange things about those lifecycle ops on the server resource (like
‘start’ seems to only be available when the server is started already, which is
pointless). But these things are not simple to fix and I don't want to use this JIRA
for them.
Domain server resource should have kill/destroy operations
----------------------------------------------------------
Key: WFCORE-2070
URL:
https://issues.jboss.org/browse/WFCORE-2070
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
The server-config resource has kill/destroy ops for the server. These should be present
on the server resource as well.
This is part of the overall user experience effort of not using server-config for
lifecycle ops, since the resource is about the config the HC uses for the server not its
runtime.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)