[
https://issues.apache.org/jira/browse/QPID-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7409:
-----------------------------
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)
was:
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
{{returnJsonIfPossible}}. If rather than returning the message's content
directly, it should first convert the message to an {{InternalMessage}} then
use the JSON serialiser to produce the bytes of the content. If the message
content cannot be expressed as JSON, it should return the content bytes as it
does today.
> Support preview of maps/list message content
> --------------------------------------------
>
> Key: QPID-7409
> URL: https://issues.apache.org/jira/browse/QPID-7409
> Project: Qpid
> Issue Type: Improvement
> Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
