You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/12/09 20:25:58 UTC
[jira] [Updated] (QPID-1686) Configuration Update removes ability
ot have multiple distinct InVM brokers.
[ https://issues.apache.org/jira/browse/QPID-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated QPID-1686:
------------------------------
Component/s: Java Broker
> Configuration Update removes ability ot have multiple distinct InVM brokers.
> ----------------------------------------------------------------------------
>
> Key: QPID-1686
> URL: https://issues.apache.org/jira/browse/QPID-1686
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Priority: Minor
>
> Before the change creating a new ApplicationRegistry with an id would result in a distinct AR.
> Now the code is littered with ApplicationRegistry.getInstance() calls which returns the AR with id 1.
> This prevents us having InVM brokers with their own config.
> The problem can be removed if the new Configuration objects form a tree so you can do:
> QueueConfig.getVHostConfig().getServerConfig()
> This could then replace the short cut of using AR.getInstance().
--
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