[
https://issues.apache.org/jira/browse/QPID-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699715#comment-14699715
]
Keith Wall commented on QPID-6696:
----------------------------------
Alex,
Looks okay, but:
# Durable flag is not respected. If the durable flag is not set we should not
be persisting the preferences provider
# I'm also puzzled about why this works for preferences providers that are
recovered? I think this is relying in a bug in
BrokerStoreUpgraderAndRecoverer#perform whichs add the
StoreConfigurationChangeListener to all objects. It should be respecting the
storage discontinuities on the model and refusing to apply the
StoreConfigurationChangeListener to any child whose parent does not
managesChildStorage.
> [Java Broker] Newly added durable preferences provider is not persisted into
> configuration store for children managing authentication providers
> Base64MD5PasswordFile and PlainPasswordFile
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6696
> URL: https://issues.apache.org/jira/browse/QPID-6696
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.0
>
> Attachments:
> 0001-QPID-6696-Add-ability-to-save-newly-added-preference.patch
>
>
> Authentication providers Base64MD5PasswordFile and PlainPasswordFile are
> configured to manage their children. As result, they are responsible for
> storing children themselves. They successfully manage User children.
> However, newly added preference provider is not stored and desappears from
> Broker model after restart.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
