You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2016/08/22 09:44:21 UTC

[jira] [Resolved] (QPID-7365) [Java Broker] Allow SystemConfig to be used for other models - not just Brokers

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

Rob Godfrey resolved QPID-7365.
-------------------------------
    Resolution: Fixed

> [Java Broker] Allow SystemConfig to be used for other models - not just Brokers
> -------------------------------------------------------------------------------
>
>                 Key: QPID-7365
>                 URL: https://issues.apache.org/jira/browse/QPID-7365
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
>             Fix For: qpid-java-6.1
>
>
> Currently the SystemConfig class is couple to the Broker model... however there is no reason why we shouldn't allow the same infrastructure to be used to create AMQP intermediaries of different types (bridges / load balancers / connection concentrators / etc) with the configuration being used to determine the nature of the intermediary to be constructed.
> The SystemConfig class should be changed to remove the dependency on the Broker Model



--
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