[
https://issues.jboss.org/browse/WFCORE-3337?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3337:
------------------------------------------
Never mind, kind of. You want to check the original thing being removed and trigger
reload-required instead of removing, which is a different thing. The WFCORE-1106 thing
might then be useful to prevent subsequent config changes that might assume the removed
things is gone from taking effect. But that's a further step.
Logging resources shouldn't be allowed to removed if they are
in-use
--------------------------------------------------------------------
Key: WFCORE-3337
URL:
https://issues.jboss.org/browse/WFCORE-3337
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Currently you can remove a logging resource even if it's used by another resource. An
example of this would be the ability to remove a formatter even though that formatter is
attached to a handler. Removing handlers does validate it's not attached to a logger
first. However all logging resources should do this.
Note that logging does not use services which is why this needs to be manually checked.
This should be doable via the configuration API. Note too that a fix to validate this will
also be done in the logmanager, LOGMGR-179.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)