[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041584#comment-13041584
]
Claus Straube commented on CAMEL-3983:
--------------------------------------
Ioannis, I think there is no 'normal usage'. I've taken the perhaps mostly used
wire component (jms) and tested their behavior. I you're doing something like
this (tested with 2.7.1):
{code}
...
from("direct://in")
.to("activemq://foo");
from("activemq://foo")
.to("mock://out");
...
{code}
You will get back message body + headers, but a different exchange id. If you
change to "activemq://foo?transferExchange=true" you will get the same result
but equal exchange ids.
I copied this behavior for hazelcast:seda. That's it. If it's not the common
behavior, we must change it (and create a ticket for the jms component ;)
> Added Support for Serialization and Message Headers to Hazelcast SEDA
> functionality
> -----------------------------------------------------------------------------------
>
> Key: CAMEL-3983
> URL: https://issues.apache.org/jira/browse/CAMEL-3983
> Project: Camel
> Issue Type: New Feature
> Components: camel-hazelcast
> Affects Versions: 2.8.0
> Reporter: Claus Straube
> Fix For: Future
>
> Attachments: SEDA-CAMEL-3983.patch, hazelcast_seda_headers_04.diff,
> hazelcast_seda_serialization_and_headers_01.diff,
> hazelcast_seda_serialization_and_headers_02.diff,
> hazelcast_seda_serialization_and_headers_03.diff
>
>
> The current implementation looses headers that are given to a
> 'hazelcast:seda:foo' route and is has problems serializing complex objects
> inside body that are not serializable.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
