camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Straube (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3983) Added Support for Serialization and Message Headers to Hazelcast SEDA functionality
Date Thu, 02 Jun 2011 06:32:47 GMT


Claus Straube commented on CAMEL-3983:

First SEDA (Staged Event Driven Architecture) is an architecture pattern. Which is something
like a poor mans actor model where components within an application are loosely coupled over
mailboxes. All you've described are not unusual use cases for a queue, they can be used to
build a SEDA, but they can be used in other scenarios as well. So why shouldn't we port this
functionality into hazelcast:queue?

"It works in the same way as the plain SEDA component but by using the hazelcast underneath,
distribution can scale not only cross threads but it can scale cross different machines...."
- I wish it would (If it would, it makes sense to have a hazelcast:seda component)...

Camel seda:
template.sendBodyAndHeader("seda:a", "foo", "my-header", "foo_");
Exchange ex = consumer.receive("seda:a", 5000);
assertEquals("foo_", ex.getIn().getHeader("my-header"));

Hazelcast seda:
template.sendBodyAndHeader("hazelcast:seda:a", "foo", "my-header", "foo_");
Exchange ex = consumer.receive("hazelcast:seda:a", 5000);
assertEquals("foo_", ex.getIn().getHeader("my-header"));

The first one is green, the second one is read. It works *NOT* the same way. Sorry. 

> Added Support for Serialization and Message Headers to Hazelcast SEDA functionality
> -----------------------------------------------------------------------------------
>                 Key: CAMEL-3983
>                 URL:
>             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,
> 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:

View raw message