[
https://issues.apache.org/jira/browse/ARTEMIS-3556?focusedWorklogId=677928&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-677928
]
ASF GitHub Bot logged work on ARTEMIS-3556:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Nov/21 22:24
Start Date: 05/Nov/21 22:24
Worklog Time Spent: 10m
Work Description: erwindon opened a new pull request #3841:
URL: https://github.com/apache/activemq-artemis/pull/3841
see https://issues.apache.org/jira/browse/ARTEMIS-3556
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 677928)
Remaining Estimate: 0h
Time Spent: 10m
> Artemis console should 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
> Priority: Minor
> Attachments: image-2021-11-05-23-07-36-340.png, screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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".
> Instead of providing a descriptive text for each message type, I kept it
> simple and used just the (short) java class name.
> question: should the existing 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!
> my guess is that only AMQPStandardMessage, AMQPLargeMessage, OpenwireMessage
> and CoreMessage can occur.
> sample:
> !screenshot-1.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
