camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6708) camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does not handle AMQP.BasicProperties
Date Sat, 12 Oct 2013 16:36:42 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793403#comment-13793403
] 

Daniel Williams commented on CAMEL-6708:
----------------------------------------

I'm submitting a new patch that takes into account pure POJO accesses instead of reflection.
 

> 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.2, 2.13.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message