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 2017/04/17 19:57:41 UTC
[jira] [Resolved] (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:all-tabpanel ]
Justin Bertram resolved ARTEMIS-235.
------------------------------------
Resolution: Won't Fix
As far as I can tell the Stomp protocol already defines uses for content-length and content-type and I I'm not aware of any violations in the code-base.
> 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
> Assignee: Justin Bertram
> Fix For: 2.next
>
>
> 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.15#6346)