Repository: qpid-dispatch Updated Branches: refs/heads/master 8c026d01f -> 0638cf52e
DISPATCH-363 - Additional fix. Removed Annotation Section references and added some examples Project: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/repo Commit: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/commit/0638cf52 Tree: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/tree/0638cf52 Diff: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/diff/0638cf52 Branch: refs/heads/master Commit: 0638cf52ed4173b350546e8dc5a5ffae2c2013cb Parents: 8c026d0 Author: Ganesh Murthy <[email protected]> Authored: Wed Jun 15 16:01:11 2016 -0400 Committer: Ganesh Murthy <[email protected]> Committed: Wed Jun 15 16:01:11 2016 -0400 ---------------------------------------------------------------------- doc/man/qdrouterd_conf_man.py | 40 +++++++++++++++++++++++++++++++------- 1 file changed, 33 insertions(+), 7 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/qpid-dispatch/blob/0638cf52/doc/man/qdrouterd_conf_man.py ---------------------------------------------------------------------- diff --git a/doc/man/qdrouterd_conf_man.py b/doc/man/qdrouterd_conf_man.py index 92e2835..b627a51 100644 --- a/doc/man/qdrouterd_conf_man.py +++ b/doc/man/qdrouterd_conf_man.py @@ -71,16 +71,42 @@ The configuration file is made up of sections with this syntax: ... } -There are two types of sections: -*Configuration sections* correspond to configuration entities. They can be queried and -configured via management tools as well as via the configuration file. -*Annotation sections* define a group of attribute values that can be included in -one or more entity sections. +For example you can define a router using the "router" section -For example you can define an "sslProfile" annotation section with SSL credentials -that can be included in multiple "listener" entities. Here's an example, note +:: + + router { + mode: standalone + id: Router.A + ... + } + +or define a listener using the "listener" section + +:: + + listener { + host: 0.0.0.0 + port: 20102 + saslMechanisms: ANONYMOUS + ... + } + +or define a connector using the "connector" section + +:: + + connector { + role: inter-router + host: 0.0.0.0 + port: 20003 + saslMechanisms: ANONYMOUS + ... + } + +"sslProfile" section with SSL credentials can be included in multiple "listener" or "connector" entities. Here's an example, note how the 'sslProfile' attribute of 'listener' sections references the 'name' attribute of 'sslProfile' sections. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
