[
https://issues.apache.org/jira/browse/QPID-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642145#action_12642145
]
Martin Ritchie commented on QPID-1103:
--------------------------------------
In a number of QpidTestCase tests we have the listed code.
The ability to create the broker should be moved in to QTC and handled
correctly.
QTC should simply take a path to a configuration file and perhaps a list of
broker versions that this test is compatible with so that it can decide to
start the test or not.
By providing a file this can be used to start internal and external java
brokers and potentially external cpp brokers.
ConfigurationFileApplicationRegistry config = new
ConfigurationFileApplicationRegistry(defaultaclConfigFile);
config.getConfiguration().setProperty("management.enabled", "false");
ApplicationRegistry.initialise(config, 1);
TransportConnection.createVMBroker(1);
> Add ability to provide a configuration file for broker start up in java test
> suite
> ----------------------------------------------------------------------------------
>
> Key: QPID-1103
> URL: https://issues.apache.org/jira/browse/QPID-1103
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M4
>
>
> Summary:
> Currently it is not possible to use a configuration file to configure an InVM
> broker. This would be helpful so we can use real configurations rather than
> the Null Registry.
> Ideally C++ and Java brokers would share configuration format so the same
> format can be used by both broker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
