[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041201#comment-13041201
]
Claus Straube commented on CAMEL-3983:
--------------------------------------
Claus, the current patch offers no more internal magic ;) But... My use case
is, that I need not only the message body, but the headers, too. That's it.
While implementing it, I thought that serialization support out of the box
would be nice. But I agree, that it must not be part of the component. And I
think it was a bad idea to mix up two subjects in one ticket ;) The message
header is the really important thing for me.
I think the cleanest solution is the one closest to the common way of
implementing Camel remoting components. In the big picture of Camel the
DefaultExchangeHolder behavior is perhaps exactly what we want. It's not a big
deal to add it. The really major issue is the message header.
> 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
