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

Ken Giusti commented on DISPATCH-1659:
--------------------------------------

While it's true that JSON syntax does not define a comment, the current config 
syntax minus comments is still not JSON parse-able. IOW after stripping out 
comments, the resulting text is not JSON.

Having a pre-parse phase that simply strips out comments is trivial from a 
support point of view - I'm fine with keeping that extension. It's the pile of 
bespoke parsing and processing code we have to maintain in the router that 
simply converts the bespoke syntax to and from JSON that I'm proposing we 
deprecate.  In the end it's JSON that we feed into the python management agent 
- I'm proposing we cut out the translation layer.

In any case it's just a "wish" that's particularly of interest as I'm now 
struggling to get the bespoke layer to correctly recognize attributes that are 
maps - both for config parsing and test config generation.   If this were JSON 
I'd be done already.
 

> Deprecate bespoke config file format for proper JSON
> ----------------------------------------------------
>
>                 Key: DISPATCH-1659
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1659
>             Project: Qpid Dispatch
>          Issue Type: Wish
>          Components: Management Agent
>    Affects Versions: 1.12.0
>            Reporter: Ken Giusti
>            Priority: Minor
>             Fix For: 2.0.0, Backlog
>
>
> The format of the qdrouterd.config file is not JSON compliant.  Instead it is 
> some bespoke quasi subset of JSON with custom comment syntax and whitespace 
> formatting restrictions.
> This bespoke format has (at least) two disadvantages:
> 1) users cannot leverage the plethora of JSON tooling available for config 
> generation
> 2) increased development/maintenance effort to support the bespoke format.
> This is a proposal to deprecate support for the non-JSON configuration file 
> format in favor of a JSON compliant file format.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to