[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioannis Polyzos updated CAMEL-3983:
-----------------------------------
Attachment: SEDA-CAMEL-3983.patch
@Claus.S your solution is very nice and elegant, however I agree with @Claus.I
that it would not be a good idea to take a different path that the rest of the
remoting components and magically marshal objects that are not serializable.
From a quick grep in the components source base I saw that
*DefaultExchangeHolder* is widely used from several components e.g mina, jms ,
netty and others, and I believe it would be good solution.
I attach here a patch with a POC test case for your consideration.
> 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: SEDA-CAMEL-3983.patch,
> 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
