You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Erwin Dondorp (Jira)" <ji...@apache.org> on 2021/11/05 22:08:00 UTC

[jira] [Created] (ARTEMIS-3556) Artemis console shoud show the message (protocol) type

Erwin Dondorp created ARTEMIS-3556:
--------------------------------------

             Summary: Artemis console shoud show the message (protocol) type
                 Key: ARTEMIS-3556
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3556
             Project: ActiveMQ Artemis
          Issue Type: Improvement
          Components: Web Console
    Affects Versions: 2.20.0
            Reporter: Erwin Dondorp
         Attachments: image-2021-11-05-23-01-34-897.png, image-2021-11-05-23-07-28-752.png, image-2021-11-05-23-07-36-340.png

When browsing messages in the Artemis Console, the page does not show the message protocol type. Expert users could derive that information from the available message keys, but there is no formal indication of the message protocol type.

Note that the message protocol type should not be confused with the message payload type.
 message protocol type is e.g.: CORE, AMQP, etc.
 message payload type is e.g.: Text, Map, Stream, etc.

I have prepared a PR that shows the message protocol type in the "Headers" table when viewing message details. The new field is "messageType". due to the list being alphabetic, it will show up just below "messageID".

I kept it simple. Instead of providing a descriptive text for each message type, I've simply used the (short) java class name.

question: should the field "type" be renamed to "payloadType" to prevent any confusion? I updated the descriptive text for "type" to better describe it.

The following class diagram shows which message types may be shown:
 !image-2021-11-05-23-07-36-340.png!



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