qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6418) [Java Broker] Use annotation to denote managed object which manage the storage of their childrens' data
Date Fri, 27 Feb 2015 14:35:04 GMT

    [ https://issues.apache.org/jira/browse/QPID-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340196#comment-14340196
] 

Justin Ross commented on QPID-6418:
-----------------------------------

Reviewed by Keith.  Approved for 0.32.

> [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
>    Affects Versions: 0.31
>            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


Mime
View raw message