qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-3026) The ApplicationRegistry object should be a singleton
Date Tue, 12 Jul 2011 11:34:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robbie Gemmell resolved QPID-3026.

    Resolution: Fixed

Closing out, patch applied.

> 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: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.11
>         Attachments: 0005-QPID-3026-remove-incomplete-support-for-multiple-App.patch
> 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

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

View raw message