[AMQ-739] STOMP transport handles JMS type improperly

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 4.0, 4.0.1
• Component/s: Transport

Environment

sending from STOMP to JMS

• Assignee: Nathan Christopher Mittler
• Reporter: Nathan Christopher Mittler
• Created: 08/Jun/06 00:23
• Updated: 21/Jun/06 18:02
• Resolved: 21/Jun/06 18:02

Description

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.