qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-1686) Configuration Update removes ability ot have multiple distinct InVM brokers.
Date Fri, 09 Dec 2016 20:25:58 GMT

     [ 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


Mime
View raw message