[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041196#comment-13041196
]
Claus Ibsen commented on CAMEL-3983:
------------------------------------
I actually think this is going down the wrong path with adding too much cruft
to components. If people have objects in their headers and they are not
serializable then they should not magically be marshalled to something XML when
sending over the wire.
If people wanna exchange data then they can make sure their objects is
serializable or in some format thats serialized out of the box: xml, json.
There are many other remoting components in Camel that does not do this. So why
should this component?
So before we go commit code. I think we need a sound use-case where this make
sense.
> 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
