[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043231#comment-13043231
]
Claus Straube commented on CAMEL-3983:
--------------------------------------
Ioannis, I don't thing we're getting a result with discussion. Our both
positions are clear (if I understood correctly):
You're saying, that seda is an internal component, but as it can reached simply
from outside / other components, it's better send a body per default. If
someone wants to send the headers, he has to set transferExchange to true. So
the default behavior is not like the camel seda component, but like other
components (mina, netty, etc.).
I'm saying, that seda is an internal component and should used internally in
the same application (so the dependency to camel is not problem). If someone
produces a message with hazelcast:seda and consumes it with something different
he uses it not in a correct way. So it's okay, that he fails with the message
headers. So the default behavior is like the camel seda component, but not like
others (mina, netty, etc.).
I think there're good reasons for both positions. There're patches for both
positions and now one of Apache Camel committers has to decide which position
fits best into the overall Camel strategy. We could discuss endless, but I
don't think that we would get a consensus in this case ;)
> 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
