[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034788#comment-13034788
]
Claus Straube edited comment on CAMEL-3983 at 5/17/11 2:33 PM:
---------------------------------------------------------------
Solved the problem by storing body and headers in a 'lightweight' message
object, which is serialized with xstream (producer). On consumer side the
message will be deserialized and headers / body will be stored in the exchange.
was (Author: clausstraube):
Solved the problem by storing body and headers in a 'light' message object,
which is serialized with xstream (producer). On consumer side the message will
be deserialized and headers / body will be stored in the exchange.
> 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
