[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041993#comment-13041993
]
Claus Straube commented on CAMEL-3983:
--------------------------------------
Ioannis, I think hazelcast:seda and JMS / SEDA are very close together. Both
(JMS / SEDA) deliver headers. So why should hazelcast:seda transport no
headers? We have no hazelcast:seda spec - so we are free to decide if we
deliver them or not. I would await if I send a message with headers over some
kind of queuing functionality (what jms and seda / hazelcast:seda are) that
they will provided on consumer side, too. An other thing would be e.g.
hazelcast:map. Here it doesn't make sense to store headers.
Can you give a reason why not to send headers?
> 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
