You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2015/02/26 16:07:06 UTC

[jira] [Resolved] (QPID-6418) [Java Broker] Use annotation to denote managed object which manage the storage of their childrens' data

     [ https://issues.apache.org/jira/browse/QPID-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey resolved QPID-6418.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 6.0 [Java]

> [Java Broker] Use annotation to denote managed object which manage the storage of their childrens' data
> -------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6418
>                 URL: https://issues.apache.org/jira/browse/QPID-6418
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
>             Fix For: 6.0 [Java]
>
>
> Some managed objects (such as the file based group provider, and file based authentication providers, as well as virtual host nodes) manage the storage of configured object implementation themselves rather than storing in the parent (broker) configuration.  Rather than use a specific exclude (which currently only excludes virtual host nodes), use annotation properties to denote types where the child objects should not be stored in the common configuration store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org