You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2016/06/08 06:31:21 UTC

[jira] [Commented] (ARTEMIS-235) Map content-type to message type on Stomp

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

Lionel Cons commented on ARTEMIS-235:
-------------------------------------

This issue is unresolved and marked as to be fixed for 1.1.1. However, 1.2.0 has already been released...

Could it be targeted for 1.3.0 instead?

> Map content-type to message type on Stomp
> -----------------------------------------
>
>                 Key: ARTEMIS-235
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-235
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: clebert suconic
>             Fix For: 1.1.1
>
>
> As documented at https://activemq.apache.org/artemis/docs/1.0.0/interoperability.html#sending-and-consuming-stomp-message-from-jms-or-apache-activemq-artemis-core-api
> Will convert bytes message or text message when the size is available. 
> it would been better to use content-type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)