You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/11/04 15:38:00 UTC

[jira] [Work logged] (ARTEMIS-649) Improve or deprecate the HTML based JMX reports.

     [ https://issues.apache.org/jira/browse/ARTEMIS-649?focusedWorklogId=676495&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-676495 ]

ASF GitHub Bot logged work on ARTEMIS-649:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Nov/21 15:37
            Start Date: 04/Nov/21 15:37
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic merged pull request #3818:
URL: https://github.com/apache/activemq-artemis/pull/3818


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 676495)
    Time Spent: 20m  (was: 10m)

> Improve or deprecate the HTML based JMX reports.
> ------------------------------------------------
>
>                 Key: ARTEMIS-649
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-649
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: John D. Ament
>            Assignee: Justin Bertram
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> ActiveMQServerControlImpl, JMSServerManagerImpl uses Java to generate HTML, for a status report
> This can be done better with templating tools like freemarker or velocity, and alleviate the manual string manipulation.  We can also leverage the type safe POJOs.
> Or, it looks like these methods are generally not recommended for use (see discussion below).  Based on this, we may want to consider deprecating instead of replacing.



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