[QPID-7409] Support preview of maps/list message content

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-6.1
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 31/Aug/16 11:38
• Updated: 02/Oct/19 19:21
• Resolved: 09/Nov/16 15:39

Description

When viewing messages through the web management console, if the message is of type such as a list or map currently the user sees the bytes of the underlying AMQP datastructure. Instead, the preview area should display the data in a human friendly way.

The managed operation Queue#getMessageContent will be enhanced to be capable of returning a message in JSON format if possible with an optional parameter returnJson. If rather than returning the message's content bytes directly, it should first convert the message to an InternalMessage (MessageConverterRegistry.getConverter(serverMessage.getClass, InternalMessage.class).convert(...)) then use the JSON serialiser to serial the MessageBody of the resulting internal message.

Within the WMC, if the resulting object is of a previewable type (string, map, list etc) and the content is not too long, the content should be added to a scrollable preview pane of the message dialogue by traversing the object tree and producing a human readable representation of its structure and content. (Perhaps an approach such as https://stackoverflow.com/questions/13341373/render-arbitrary-json-in-html will help)

Issue Links

• is related to: QPID-7382 Message dialogue tries to inline the text of a text message content regardless of the its length