[jboss-jira] [JBoss JIRA] (WFCORE-3337) Logging resources shouldn't be allowed to removed if they are in-use

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473483#comment-13473483 ] 

Brian Stansberry edited comment on WFCORE-3337 at 10/6/17 12:05 PM:
--------------------------------------------------------------------

Nope, capabilities don't have to expose services. Definitely if all the wiring between your resources was tracked via caps/reqs then you would get standard failure behavior if people tried to break model integrity.


was (Author: brian.stansberry):
Nope, capabilities don't have to expose services.

> 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)