[AMQ-2833] Fix to STOMP Transport fixing message type selection

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.4.0
• Component/s: Transport

Environment

STOMP clients which always sets the content-length header in out going messages

• Patch Info: Patch Available
• Assignee: Robert Davies
• Reporter: Mark Eschbach
• Created: 16/Jul/10 22:55
• Updated: 19/Jul/10 16:11
• Resolved: 19/Jul/10 16:11

Description

Ruby's STOMP client always sets the content-length header and does not provide a mechanism to override the behavior. In addition, the 1.0 STOMP specification states the content-length header is optional but recommended. I implemented the feature discussed in AMQ-739 utilizing the 'amq-msg-type' header to select the message type. I've only implemented 'text' and 'byte' message types.