[jira] Updated: (QPID-197) Consistent configuration for C++ and Java brokers.

["Martin Ritchie (JIRA)" <qp...@incubator.apache.org>]

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

Martin Ritchie updated QPID-197:
--------------------------------

    Fix Version/s: M3

> Consistent configuration for C++ and Java brokers.
> --------------------------------------------------
>
>                 Key: QPID-197
>                 URL: https://issues.apache.org/jira/browse/QPID-197
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker, C++ Client, Dot Net Client, Java Broker, Java Client, Java Common, JMS Compliance
>            Reporter: Alan Conway
>             Fix For: M3
>
>
> Define a consistent configuration story between the C++ and Java brokers. 
> - Define a common configuration model: naming conventions, type system.
> - Define standard configuration settings for features suported in both brokers.
> - Define naming conventions to avoid using the same config name with different meanings in each broker
> The brokers will have some language specific settings for things that are different between the two, but wherever it's reasonable we should define common settings. 
> Both brokers will support multiple config formats (e.g. XML, property file, boost config file, the set of supported formats will be different (e.g. Java properties vs C++ command line args)
> The brokers may or may not share a common file format, depending on the solutions adopted by each. If they do share a common format, it should be possible to identify common vs. language specific settings so either broker can  use the same config file without being confused by settings intended for the other.
> See also: QPID-104

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.