[
https://issues.apache.org/jira/browse/DISPATCH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated DISPATCH-1656:
---------------------------------
Description:
This feature would add a new "openProperties" attribute to the
org.apache.qpid.dispatch.connector and org.apache.qpid.dispatch.listener
management entities. This new attribute is type string and is optional.
If supplied it will consist of a series of one or more field entries separated
by commas. A field entry is text in the form "key: value", where "key" that can
be encoded as a valid AMQP 1.0 Symbol type. Value will be encoded as an AMQP
1.0 String type.
The key or value text may contain spaces, colons or commas but must be enclosed
in single quotes (see example below).
Key values that start with *qd.* or *x-opt-qd.* are reserved and must not be
used.
In addition, the following keys are reserved and must not be used:
product
version
failover-server-list
network-host
port
scheme
hostname
The openProperties keys and values will be merged into the connection
properties field of outgoing Open performative when establishing or accepting
connections.
The openProperties attribute is NOT allowed on connector or listener entities
with roles of either "inter-router" or "edge".
The openProperties attribute is NOT allowed on listener entities than enable
http, i.e. http: true.
Example:
{{connector {}}
{{ name: broker}}
{{ role: route-container}}
{{ host: 127.0.0.1}}
{{ port: 22180}}
{{ saslMechanisms: ANONYMOUS}}
{{ *openProperties: "foo: bar,baz:foo, bar: 'Hello: you big, wonderful
world!'"*}}
{{}}}
was:
This feature would add a new "openProperties" attribute to the
org.apache.qpid.dispatch.connector and org.apache.qpid.dispatch.listener
management entities. This new attribute is type string and is optional.
If supplied it will consist of a series of one or more field entries separated
by commas. A field entry is text in the form "key: value", where "key" that can
be encoded as a valid AMQP 1.0 Symbol type. Value will be encoded as an AMQP
1.0 String type.
Key and value may contain spaces or colons but must be enclosed in single
quotes (see example below).
Key values that start with *qd.* or *x-opt-qd.* are reserved and must not be
used.
In addition, the following keys are reserved and must not be used:
product
version
failover-server-list
network-host
port
scheme
hostname
The openProperties keys and values will be merged into the connection
properties field of outgoing Open performative when establishing or accepting
connections.
The openProperties attribute is NOT allowed on connector or listener entities
with roles of either "inter-router" or "edge".
The openProperties attribute is NOT allowed on listener entities than enable
http, i.e. http: true.
Example:
{{connector {}}
{{ name: broker}}
{{ role: route-container}}
{{ host: 127.0.0.1}}
{{ port: 22180}}
{{ saslMechanisms: ANONYMOUS}}
{{ *openProperties: "foo: bar,baz:foo, bar: 'Hello: world!'"*}}
{{}}}
> Allow user-configured connection properties in the Open performative
> --------------------------------------------------------------------
>
> Key: DISPATCH-1656
> URL: https://issues.apache.org/jira/browse/DISPATCH-1656
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Router Node
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
> Fix For: 1.13.0
>
>
> This feature would add a new "openProperties" attribute to the
> org.apache.qpid.dispatch.connector and org.apache.qpid.dispatch.listener
> management entities. This new attribute is type string and is optional.
> If supplied it will consist of a series of one or more field entries
> separated by commas. A field entry is text in the form "key: value", where
> "key" that can be encoded as a valid AMQP 1.0 Symbol type. Value will be
> encoded as an AMQP 1.0 String type.
> The key or value text may contain spaces, colons or commas but must be
> enclosed in single quotes (see example below).
> Key values that start with *qd.* or *x-opt-qd.* are reserved and must not be
> used.
> In addition, the following keys are reserved and must not be used:
> product
> version
> failover-server-list
> network-host
> port
> scheme
> hostname
> The openProperties keys and values will be merged into the connection
> properties field of outgoing Open performative when establishing or accepting
> connections.
> The openProperties attribute is NOT allowed on connector or listener entities
> with roles of either "inter-router" or "edge".
> The openProperties attribute is NOT allowed on listener entities than enable
> http, i.e. http: true.
> Example:
> {{connector {}}
> {{ name: broker}}
> {{ role: route-container}}
> {{ host: 127.0.0.1}}
> {{ port: 22180}}
> {{ saslMechanisms: ANONYMOUS}}
> {{ *openProperties: "foo: bar,baz:foo, bar: 'Hello: you big, wonderful
> world!'"*}}
> {{}}}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
