[
https://issues.apache.org/jira/browse/QPID-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899226#comment-15899226
]
ASF subversion and git services commented on QPID-7365:
-------------------------------------------------------
Commit 1785824 from [~lorenz.quack] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1785824 ]
QPID-7647: [Java Broker] Fix handling of broker type in configuration
merged from 6.1.x branch:
$ svn merge -c1785819 https://svn.apache.org/repos/asf/qpid/java/branches/6.1.x
resolved conflicts:
* reverted changes to ConfiguredObjectRecordConverter since they pertained to
changes introduced by QPID-7365 on 6.1.x
* fixed minor refactoring conflict in BrokerStoreUpgraderAndRecovererTest
> [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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
