[
https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042234#comment-13042234
]
Claus Straube commented on CAMEL-3983:
--------------------------------------
Ioannis, as I wrote before, I understand what the problem is. What I don't
understand is, why we need a seda prefix, if we use it like a normal queue? All
features of the seda implementation can be build into the queue implementation
with three or four options (concurrentConsumers, pollIntervall, operation,
transferExchange) - without having an obviously confusing name. And without
much effort (like they did on JMS). I see hazelcast:seda in a line with seda
and vm - the only difference is, that your not bound to camel context or a vm.
That means for internal use inside a camel application. If you want to use it
externally, take hazelcast:queue. And a seda queue is a very simple thing.
There're not hundreds of applications grabbing for data (like this can be on
hazelcast:map). There're two parties: a producer and a consumer. And yes, of
course there can be one who registers a hazelcast:queue listener on the seda
queue, but to my humble opinion - there better ways in camel *and* hazelcast to
get this kind of information.
So finally: If we decide to act like a 'normal' queue, my question is why do we
need something that's not named queue?
> 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
