Take message properties into account on sending #28
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
|
Please rebase against |
Priority, delivery mode, and expiration aren't taken into account on sending when set in the JMS message. This is compliant with the specifiation though. This commit provide a flag in RMQConnectionFactory to make the RMQMessageProducer use the message properties if set. This is non-compliant with the specification but more natural. The existing and spec-compliant behavior is still the default. Fixes #26
acogoluegnes
force-pushed
the
rabbitmq-jms-26
branch
from
9f4414d
to
5819b6b
Compare
|
Done. |
michaelklishin
approved these changes
Jun 15, 2017
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.
Priority, delivery mode, and expiration aren't taken into
account on sending when set in the JMS message. This is compliant with
the specifiation though. This commit provide a flag in
RMQConnectionFactory to make the RMQMessageProducer use the
message properties if set. This is non-compliant with the specification
but more natural. The existing and spec-compliant behavior is still
the default.
Fixes #26