camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Cosentino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10291) Camel RabbitMQ invalid handling of message timestamp
Date Tue, 06 Sep 2016 06:06:21 GMT

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

Andrea Cosentino commented on CAMEL-10291:
------------------------------------------

Thanks for the PR :-)

> Camel RabbitMQ invalid handling of message timestamp
> ----------------------------------------------------
>
>                 Key: CAMEL-10291
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10291
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-rabbitmq
>    Affects Versions: 2.17.3
>            Reporter: Florian Gessner
>            Assignee: Andrea Cosentino
>              Labels: github-pullrequest, patch
>             Fix For: 2.18.0
>
>
> At the moment the RabbitMQ component is does not map the timestamp of a message appropriately.
The outbound mapping (producer) expects the timestamp of the camel message is of type String
whereas the String is just the long value representing the timestamp. However the timestamp
is already a java.util.Date when the producer just forwards a message from a rabbitmq consumer
as the timestamp is already a java.util.date as define in AMQP.BasicProperties.
> The provided pull request provides a compatible change. So it still keeps the old behaviour
as fallback so that the long value is evaluated if the provided data is not a java.util.Date



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message