[
https://issues.apache.org/activemq/browse/CAMEL-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44594#action_44594
]
Jonathan Anstey commented on CAMEL-756:
---------------------------------------
After further inspection, this is a known Qpid bug. See:
https://issues.apache.org/jira/browse/QPID-1092. The fix has been merged
already so the next Qpid release should work.
As for the workaround I mentioned, it wouldn't work as well as I thought. By
not using Qpid's ObjectMessage (and just using BytesMessage) Camel would have
no way of knowing it had to auto deserialize the byte array back to an Object.
This would actually be more confusing to the user IMO.
I guess we'll just have to wait until Qpid gets released again?
> AMQP component can't send an ObjectMessage
> ------------------------------------------
>
> Key: CAMEL-756
> URL: https://issues.apache.org/activemq/browse/CAMEL-756
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Jonathan Anstey
> Fix For: 1.5.0
>
>
> Sending a TextMessage and BytesMessage work fine but when you try to send a
> Serializable object it gets lost somehow... see the
> testJmsRouteWithObjectMessage test in
> http://svn.apache.org/repos/asf/activemq/camel/trunk/components/camel-amqp/src/test/java/org/apache/camel/component/amqp/AMQPRouteTest.java
> to see what happens.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
