You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/08/31 11:43:20 UTC
[jira] [Updated] (QPID-7409) Support preview of maps/list message
content
[ 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 {{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.
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.
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org