camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Polyzos (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-3983) Added Support for Serialization and Message Headers to Hazelcast SEDA functionality
Date Thu, 02 Jun 2011 08:11:47 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042642#comment-13042642
] 

Ioannis Polyzos commented on CAMEL-3983:
----------------------------------------


 Earlier I have not described the SEDA architecture but how the SEDA *component* works, and
I have noted that works like a *work queue*.
 
 What I have stated as a difference is that in case someone use the hazelcast:queue, an event
will broadcast to all consumers, while in the case of hazelcast:seda only to one.

 It is very reasonable that your example does not work because in the current implementation
does not transfer headers, and this is what the patch SEDA-CAMEL-3983-2.patch provide. But
even in the case you have used this code you have note used the "transferExchange" option.
If you please refer to the test cases of patch for examples on usage...

  

> 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

Mime
View raw message