[jira] [Commented] (QPID-7469) [Java Broker] Improve VirtualHost#publishMessage

["Alex Rudyy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607970#comment-15607970 ] 

Alex Rudyy commented on QPID-7469:
----------------------------------

We need to add field  ContentTransferEncoding into ManagableMessage to indicate whether message body is base64-encoded or not.
ContentTransferEncoding can be set to the following values:
base64 - body is encoded with base64
identity - body is not encoded; no transformation is needed. Default.

ContentTransferEncoding is case insensitive.

Depending from ContentTransferEncoding  and MimeType the following should happen:

Mime type make sense only when json body is a string.

* If mime type is set and body is not a string we should reject the message.
* If json body is a string:
** when transfer encoding is not set and mime type is not text/* then reject the message
*** if charset is in mime type we need to reject the message
** if transfer encoding is base64 we base64 decode, otherwise treat is as string

Note, we can get byte array via amqp management


> [Java Broker] Improve VirtualHost#publishMessage
> ------------------------------------------------
>
>                 Key: QPID-7469
>                 URL: https://issues.apache.org/jira/browse/QPID-7469
>             Project: Qpid
>          Issue Type: Task
>          Components: Java Broker
>    Affects Versions: qpid-java-6.1
>            Reporter: Lorenz Quack
>
> * When the POST request to VirtualHost#publishMessage does not contain a body there is a ServerError
> * When the mimeType is set the message content is always interpreted as base64.



--
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