[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041192#comment-13041192
]
Claus Straube commented on CAMEL-3983:
--------------------------------------
Hi Ioannis. With DefaultExchangeHolder every Object that is not serializable
will be skipped. I don't know, if we want this. The current patch (version 3),
offers the possibility to add a serializer implementation as option. So the
user has the choice to transport only serializable Objects, or provide a
implementation that can serialize Objects that don't implement serialzable
(e.g. xStreams).
> 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: 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
