[
https://issues.apache.org/jira/browse/DISPATCH-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221768#comment-15221768
]
Chuck Rolke commented on DISPATCH-202:
--------------------------------------
Config files still do not allow map attribute types but Dispatch config now
accepts .json files in addition to .conf files. This feature was part of the
policy commit
https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=48e8162 in
DISPATCH-188.
A side-by-side comparison of an easy configuration is in tests/config-1 where
files A.conf and A.json hold identical config data.
> Config files do not allow attribute type 'map'
> ----------------------------------------------
>
> Key: DISPATCH-202
> URL: https://issues.apache.org/jira/browse/DISPATCH-202
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 0.5
> Reporter: Chuck Rolke
> Assignee: Alan Conway
>
> Config file preprocessing clobbers a json map.
> A workaround could be to key off the file extension. If the extension is
> '.json' then load the file as straight json else go ahead with the current
> processing.
> Some of the preprocessing supports an older config file format which is not
> needed going forward. Supporting pure json has other advantages. One
> exception to the 'pure json' goal is to allow lines starting with '#' as
> comments that are stripped out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
