[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036032#comment-13036032
]
Claus Ibsen commented on CAMEL-3983:
------------------------------------
I dont see we should couple hazlecast with a fixed serialization
framework/protocol. End users should be able to pick and chose what they want
to use. Some may want xstream, jaxb, others json, google protobuf, just
serialized objects etc.
> 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: Improvement
> Affects Versions: 2.8.0
> Reporter: Claus Straube
> Fix For: 2.8.0
>
> Attachments: hazelcast_seda_serialization_and_headers_01.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
