[
https://issues.jboss.org/browse/WFCORE-289?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFCORE-289:
-----------------------------------------
It's easier to implement with these notifications coming from server-config=YYY but it
would be nicer to have them from /host=XXX/server=YYY on both the HC process and, perhaps,
on the server itself. Although having them on the server itself needs thought, as the
notification should likely be different, and oriented toward that server's own
point-of-view and not that of a controlling HC.
Anyway, it's nicer to have the HC ones in /host=XXX/server=YYY as that is the resource
that represents the server. The server-config resource is just a chunk of configuration
data. It has start/stop ops, but really that just because in the past we hadn't
figured out how to have those ops on the server resource itself, so we stuck them on the
next best spot. Let's try and not go down that path again.
Emit notifications for servers in domain mode
---------------------------------------------
Key: WFCORE-289
URL:
https://issues.jboss.org/browse/WFCORE-289
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
emit notifications related to server lifecycle in domain mode:
* server-started
* server-stopped
* server-restarted
* server-destroyed
* server-killed
These notifications should be emitted from the corresponding server-config resource
(under /host=XXX/server-config=YYY)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)