You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/07/05 18:36:11 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=15362970#comment-15362970 ] 

Justin Bertram commented on ARTEMIS-235:
----------------------------------------

Perhaps I'm missing something, but in what way is this issue "marked as to be fixed for 1.1.1"?

Also, this JIRA can't be targeted for 1.3.0 because 1.3.0 has already been released.

> 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, 1.2.0, 1.3.0
>            Reporter: clebert suconic
>             Fix For: 1.4.0
>
>
> 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)