[
https://issues.apache.org/jira/browse/ARTEMIS-4955?focusedWorklogId=928131&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-928131
]
ASF GitHub Bot logged work on ARTEMIS-4955:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jul/24 10:46
Start Date: 31/Jul/24 10:46
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #5120:
URL:
https://github.com/apache/activemq-artemis/pull/5120#issuecomment-2260225438
I think it could be nicer to use an extension=type setup to convey what type
of config is being used, rather than using e.g broker.properties files for
different types of config. Seems more obvious for now, and more open to
addition later for other specific types at some point? E.g think of the log4j
config as example.
Issue Time Tracking
-------------------
Worklog Id: (was: 928131)
Time Spent: 20m (was: 10m)
> Support broker properties from JSON files
> -----------------------------------------
>
> Key: ARTEMIS-4955
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4955
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Domenico Francesco Bruscino
> Assignee: Domenico Francesco Bruscino
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The broker properties are low level, lower level than xml, however it is very
> powerful but the current format is too verbose and requires to escape
> characters that could be included in the broker properties: ' ', '
> ', '=', ':'. The JSON format is more compact and only requires to escape JSON
> reserved characters that are not typically used in the broker properties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
