[
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-2.patch
I would agree with Claus.I. JMS is a different scenario than ours and would be
reasonable to transfer specific headers in JMS due to the spec.
Components like netty and mina that are closer to our case follow the
aforementioned convention and transfer either the whole exchange or only the
body (please refer to the payload helpers of the components for more info).
I attach a new patch with the changes discussed earlier 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-2.patch, SEDA-CAMEL-3983.patch,
> hazelcast_seda_headers_04.diff,
> 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
