[
https://issues.apache.org/jira/browse/DISPATCH-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366244#comment-15366244
]
Robbie Gemmell commented on DISPATCH-415:
-----------------------------------------
To clarify a little, all the Java broker effectively does is essentially what
you just suggested, letting people specify properties (in a variety of ways)
that it then substitutes when using the config. It happens to default a few
properties and uses them for port numbers, so people can override them easily.
So rather than saying 5672 for the default AMQP port config (which arguably
Dispatch does have, though possibly uses service lookup to figure out the
port?) it uses the property name.
> Dynamic port allocation from the command line
> ---------------------------------------------
>
> Key: DISPATCH-415
> URL: https://issues.apache.org/jira/browse/DISPATCH-415
> Project: Qpid Dispatch
> Issue Type: New Feature
> Reporter: Adel Boutros
>
> As described in this
> [mail|http://qpid.2158936.n2.nabble.com/Qpid-Dispatch-Dynamic-port-allocation-from-the-command-line-td7646495.html],
> it would be nice if there was a way to alllocate dynamically ports from the
> command line as is the case with Qpid Java Broker
> Qpid Java Broker properties reference:
> https://qpid.apache.org/releases/qpid-java-6.0.3/java-broker/book/Java-Broker-Initial-Configuration-Configuration-Properties.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
