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

Rob Godfrey commented on QPID-6418:
-----------------------------------

Note: this will resolve a defect whereby creating a new file based group 
provider (or an authentication provider) from a file which already contains 
entries will lead to failure on broker restart due to duplicate names (since 
the children will be stored both in the external files, and in the common 
config)

> [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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to