You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2011/06/30 11:14:29 UTC
[jira] [Assigned] (QPID-3026) The ApplicationRegistry object should
be a singleton
[ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall reassigned QPID-3026:
--------------------------------
Assignee: Keith Wall (was: Andrew Kennedy)
> The ApplicationRegistry object should be a singleton
> ----------------------------------------------------
>
> Key: QPID-3026
> URL: https://issues.apache.org/jira/browse/QPID-3026
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.9
> Reporter: Andrew Kennedy
> Assignee: Keith Wall
> Priority: Minor
> Fix For: 0.11
>
>
> The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.
> Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org