You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Nathan Mittler (JIRA)" <ji...@apache.org> on 2006/06/07 20:55:51 UTC
[jira] Assigned: (AMQ-739) STOMP transport handles JMS type
improperly
[ https://issues.apache.org/activemq/browse/AMQ-739?page=all ]
Nathan Mittler reassigned AMQ-739:
----------------------------------
Assign To: Nathan Mittler
> STOMP transport handles JMS type improperly
> -------------------------------------------
>
> Key: AMQ-739
> URL: https://issues.apache.org/activemq/browse/AMQ-739
> Project: ActiveMQ
> Type: Bug
> Components: Transport
> Environment: sending from STOMP to JMS
> Reporter: Nathan Mittler
> Assignee: Nathan Mittler
> Priority: Minor
>
> 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 message.
> 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:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira