[
https://issues.apache.org/jira/browse/CAMEL-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762069#comment-13762069
]
Daniel Williams commented on CAMEL-6708:
----------------------------------------
I do agree. Perhaps it should simply be a static map of cached Method objects
initialized in a static initializer that meet the get<None>(void):Object
structure. This will allow the RabbitMQ client library to grow mutually
exclusive the camel-rabbitmq project.
> camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does
> not handle AMQP.BasicProperties
> ------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-6708
> URL: https://issues.apache.org/jira/browse/CAMEL-6708
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.12.0
> Environment: All
> Reporter: Daniel Williams
> Fix For: 2.12.1, 2.13.0
>
> Attachments: patch.txt
>
>
> RabbitMQConsumer.RabbitConsumer#handleDelivery currently does not handle
> AMQP.BasicProperties as sent from the RabbitMQ client library and passed onto
> the consumer. This poses a problem for downstream functionality.
> e.g.
> post a message to a queueA
> configure camel as from(queueA).to(queueB).end();
> pull a message from queueB
> deserialize
> If the message was pushed with header information such as Type it will be
> stripped off as the RabbitMQConsumer.RabbitConsume#handleDelivery is invoked
> cause the RabbitMQProducer to transmit to queueB without the header
> information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
