qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7322) [Java Broker] Add ability to specify Qpid vendor specific or deployment specific properties file in addition to Qpid instance properties file which can be specified with command line arguments -props
Date Thu, 12 Jan 2017 13:12:51 GMT

    [ https://issues.apache.org/jira/browse/QPID-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820962#comment-15820962
] 

Keith Wall commented on QPID-7322:
----------------------------------

We said we should layer the properties, so that any properties specified by a {{-props}} argument
overlay default system.properties.  The public API should not need to change.

> [Java Broker] Add ability to specify Qpid vendor specific or deployment specific properties
file in addition to Qpid instance properties file which can be specified with command line
arguments -props
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7322
>                 URL: https://issues.apache.org/jira/browse/QPID-7322
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Alex Rudyy
>             Fix For: qpid-java-7.0
>
>
> Currently broker properties can be specified in the following ways:
> * environment variables
> * JVM system properties
> * using command line argument ' -prop' and specifying key value pair
> * using command line argument '-props' to specify a path to a properties file
> * system.properties file in classpath if command line argument ' -props ' is not set
> * context variables on the configured objects
> In some cases when Qpid distribution is deployed into specific environments a properties
file with environment specific settings needs to be provided and bundled with Qpid distribution.
For example, some of AMQP protocols or configured objects implementations can be disabled
in such properties file. At the moment, such settings can be put system.properties file on
the classpath. However, if user will specify a path to properties file with command line option
-props, the settings in system.properties file will not be applied. We need a mechanism to
provide a Qpid environment deployment properties file in addition to instance specific properties
file specified with command line argument '-props'.



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


Mime
View raw message