[jira] [Commented] (AMQ-6186) JMS consumer receives BytesMessage when sending text message from STOMP producer

["Timothy Bish (JIRA)" <ji...@apache.org>]

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

Timothy Bish commented on AMQ-6186:
-----------------------------------

The content-type header is not a mandatory header in the later STOMP specification revision, note the SHOULD:

{quote}
SEND frames SHOULD include a content-length header and a content-type header if a body is present.
{quote}

While it would be nice to try and honor the content-type value it is not mandatory.  

> JMS consumer receives BytesMessage when sending text message from STOMP producer
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-6186
>                 URL: https://issues.apache.org/jira/browse/AMQ-6186
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.11.1
>            Reporter: Abhi
>              Labels: stomp
>
> The 'Working with JMS Text/Bytes Messages and Stomp' section on stomp wiki page (http://activemq.apache.org/stomp.html) explains how inclusion of 'content-length' header affects message transformation on ActiveMQ server.
> Now, many libraries that implement STOMP protocol v1.1,1.2 include this header is it is a mandatory header and this breaks compatibility with ActiveMQ.
> I think ActiveMQ should consider using "content-type" header to determine the type of message that is being sent instead of relying on inclusion/exclusion of content-length header.



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