camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Straube (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-3983) Added Support for Serialization and Message Headers to Hazelcast SEDA functionality
Date Tue, 24 May 2011 14:27:47 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Straube updated CAMEL-3983:
---------------------------------

    Attachment: hazelcast_seda_serialization_and_headers_02.diff

I've implemented a serialization check. So if a user stores only objects in body and headers
that are ALL serializable, these objects will be send over hazelcast as they are (so the user
is absolutely free to choose the serialization implementation he wants). If there is at least
one object inside body or headers that is not serializable, the whole message will be serialized
just for transportation (Hazelcast can't transport objects that are not serializable). Then
on consumer side the message will be deserialized. The whole serialization / deserialization
process is transparent for the user. For serialization xstream is used because of its generic
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: 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: http://www.atlassian.com/software/jira

Mime
View raw message