Use the ActiveMQ Convention of Distinguishing between TextMessage and BytesMessage #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…en converting between different wire formats.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ActiveMQ uses the presence of the content-length header to distinguish between TextMessage and BytesMessage:
http://activemq.apache.org/stomp.html (See "Working with JMS Text/Bytes Messages and Stomp".)
This is important when forwarding messages between different connector, e.g., from Stomp to OpenWire.
This change adjusts the handling of messages accordingly such that for TextMessages the content-length header is omitted.