[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042001#comment-13042001
]
Claus Straube commented on CAMEL-3983:
--------------------------------------
One additional thought... I think we have to separate components for internal
communication and external communication. Components for internal communication
are seda, vm and so on. Components for external communication are file, mina,
ftp, hazelcast:map... I think JMS can be used for both scenarios due to the
spec.
Now lets take a look on hazelcast. We have here a map, multimap, set, queue,
topic, list implementation. If we look at the camel-hazelcast implementation we
have implementations for map, multimap, queue, list and a thing called seda. So
let's map it to internal / external communication. External communication means
in this case, that a third party app gets the message (which can of course not
handle any headers). If I would implement external communication with a
hazelcast cluster I would use the components named equal to the hazelcast
implementation. So I would *not* mix up hazelcast:seda and a queue consumer on
the other side.
seda is in camel for internal communication and I think hazelcast:seda should
behave like the in memory seda. If anyone want to communicate with a external
hazelcast cluster, he's free to use hazelcast:queue (which transports only the
body).
> 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
