rgannu opened a new pull request #4346:
URL: https://github.com/apache/camel/pull/4346
The additional headers will be added on top of the existing headers
from the message.
The properties added are only basic AMQP properties as defined in the
{@link com.rabbitmq.client.AMQP.BasicProperties.Builder}. When the
message contains already these properties then will be considered and
these additional properties will be ignored.
Introduced a SimpleDataHolderBean to hold a hashmap for adding any
header. Changed the RabbitMQConstants to Enum so that we can also add
the property description in that.
As with this fix though we can add any header, only static/hard-coded
values could be associated.
The rabbitmq AMQP basic properties constant keys should not
have dot or hyphen in their prefixes. This gives problem in trying to
retrieve the value due to fix of CAMEL-15394. Changed to underscore.
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change
(usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line
and body.
- [ ] If you're unsure, you can format the pull request title like
`[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX`
with the appropriate JIRA issue.
- [ ] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
- [ ] Run `mvn clean install -Psourcecheck` in your module with source check
enabled to make sure basic checks pass and there are no checkstyle violations.
A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
