activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler (JIRA)" <>
Subject [jira] Commented: (AMQ-739) STOMP transport handles JMS type improperly
Date Tue, 20 Jun 2006 10:11:51 GMT
    [ ] 

Nathan Mittler commented on AMQ-739:

clients can use bytes and text messages so long as they follow AMQ's scheme for making the
distinction: if content-length is specified, it's a bytes message, otherwise it's text.

So I don't think any action needs to be taken on this issue other than updating AMQ's stomp
page to make it clear how to make the distinction between bytes and text using the stomp protocol.

> STOMP transport handles JMS type improperly
> -------------------------------------------
>          Key: AMQ-739
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: Transport
>     Versions: 4.0.1, 4.0
>  Environment: sending from STOMP to JMS
>     Reporter: Nathan Mittler
>     Assignee: Nathan Mittler
>     Priority: Minor
>      Fix For: 4.1

> Original Estimate: 1 week
>         Remaining: 1 week
> Sending a text message from a stomp client with a content-length results in a bytes message
on JMS.  Suggest doing the following ...
> 1) The stomp transport should always add the content-length header to out-going messages,
regardless of content-type or whether or not a content-length was provided on the incoming
> 2) The stomp transport should handle in-coming messages with a content-type header, and
should pass that through.
> 3) If a message comes in without a content-length or a content-type, it should just be
assumed a TextMessage.  This way we can use the terminating null character as the delimiter.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message