You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2017/04/18 15:53:41 UTC
[jira] [Updated] (QPID-7610) [Java Broker] MemorySystemConfig
should override the default preferenceStoreAttributes
[ https://issues.apache.org/jira/browse/QPID-7610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lorenz Quack updated QPID-7610:
-------------------------------
Attachment: 0001-QPID-7610-Java-Broker-MemorySystemConfig-should-over.patch
Not exactly a "one line change"
> [Java Broker] MemorySystemConfig should override the default preferenceStoreAttributes
> --------------------------------------------------------------------------------------
>
> Key: QPID-7610
> URL: https://issues.apache.org/jira/browse/QPID-7610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Lorenz Quack
> Priority: Minor
> Fix For: qpid-java-broker-7.0.0
>
> Attachments: 0001-QPID-7610-Java-Broker-MemorySystemConfig-should-over.patch
>
>
> The MemorySystemConfig should override the preferenceStoreAttributes and provide a "Memory" type to make embedding the broker easier.
> from an IRC conversation:
> {code}
> [...]
> <jameshowe> It would make sense if the Memory one overrode it to Memory then
> <jameshowe> no?
> <rgodfrey> yeah - or to NoOp really
> <jameshowe> It's my understanding they're used with the admin UI, so if they were Noop then something wouldn't work?
> <lorenz> yes, it looks like we could improve it
> [...]
> <rgodfrey> to the point that jameshowe makes - I agree, noop isn't really right… we want a memory type, or to have MemorySystemConfig implement the provider interface
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org