Github user jmesnil commented on the issue:
https://github.com/apache/activemq-artemis/pull/2035
@jbertram thanks for the suggestion.
In WildFly, we get all these information as a String blob from
https://github.com/apache/activemq-artemis/blob/acc34d90881313d5c94a5a377aac9438175e55ef/artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/management/ActiveMQServerControl.java#L890
In addition to this PR, we would have to unmarshall the JSON string, change
it to put back the JMS semantic and marshall it again before to send it to the
management client.
This seems brittle to rely on a JSON string for this information.
@jbertram Would it be possible to enhance ActiveMQServerControl so that it
returns a proper DTO containing all the information? In WildFly we can then
take care of all the transformation and json serialization but we would have a
proper API contract for all consumer and connection data coming from
ActiveMQServerControl
---
