[jboss-jira] [JBoss JIRA] (LOGMGR-179) The configuration API should fail if a configuration being removed is attached to another configuration

[James Perkins (JIRA)]

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

James Perkins commented on LOGMGR-179:
--------------------------------------

For most cases this can be quite easily achieved. However with POJO's this introduces some possible complexity of having to know if a POJO object is assigned to a formatter, handler, logger, filter or error manager. An mapping from the POJO name to a configuration type/name may be needed to ensure integrity.

> The configuration API should fail if a configuration being removed is attached to another configuration
> -------------------------------------------------------------------------------------------------------
>
>                 Key: LOGMGR-179
>                 URL: https://issues.jboss.org/browse/LOGMGR-179
>             Project: JBoss Log Manager
>          Issue Type: Bug
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> The configuration API will allow the removal of a configuration resource even if that resource is attached to a different configuration. For example you can remove a {{FormatterConfiguration}} even if that formatter is attached to a {{HandlerConfiguration}}. This should be validated and fail if prepared or committed via the {{LogContextConfiguration}} API.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)