[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042019#comment-13042019
]
Ioannis Polyzos commented on CAMEL-3983:
----------------------------------------
To my humble opinion, I think that the component should follow what is
described in the javadoc of the DefaultExchangeHolder, and make the transfer of
header and other information optional. To be more specific by default to
exchange only the body of the message and give the ability to exchange the
whole exchange (with headers and other info) with the use of
transferExchange=true option.
The reason of this is mainly flexibility and compliance. To be more specific,
if we make the exchange of headers the default case and mandatory with the use
of DefaultExchangeHolder the whole route flow is tighten to camel. And in case
we make it mandatory and default through the use of a custom component, the
flow is tighten specifically to the camel-hazelcast component.
In such cases we come to what Claus.S described earlier and any third party
system that may want for example to participate to this flow e.g by using the
queue or by registering any listeners to this queue it will have to import and
use of the camel libraries and be obligated to use either our custom wrapper or
DefaultExchangeHolder.
Also I believe that we should treat all the component uniformly as for
external communication (in the same way we have worked with the other
components) in order to ensure interoperability and compliance between the
camel-hazelcast components. For example the case one wants to register a
listener in the queue used from a SEDA component for statistics by using the
hezelcast:queue component.
> 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
