[
https://issues.apache.org/jira/browse/QPID-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340161#comment-14340161
]
Keith Wall commented on QPID-6418:
----------------------------------
Fix looks reasonable to me. Since this defect restricts users from using an
Broker with a preexisting passwd/groups files, I think this should be requested
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: [email protected]
For additional commands, e-mail: [email protected]
