[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040599#comment-13040599
]
Claus Ibsen commented on CAMEL-3983:
------------------------------------
The component should *not* require any 3rd party serialization framework, or
the likes. You do not know who is the receiver on the other end. Now they
suddenly get headers in XML format.
Instead end users can/must make sure to provide compliant data in the messages
they send to it.
It is however okay to add check for headers is serializable or not, and then
either
- throw an exception failing
- or log a warning.
And then maybe add an option so people can decide if they want to throw the
exception or log (and at which level, eg WARN -> DEBUG) etc.
You can also consider adding some SPI to this component. So end users can
provide custom plugins to control the marshalling / unmarshalling.
Then in your custom apps you can use the xstream if you like.
> 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
>
>
> 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
