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] [Commented] (CAMEL-3983) Added Support for Serialization and Message Headers to Hazelcast SEDA functionality
Date Mon, 30 May 2011 10:28:47 GMT

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

Claus Straube commented on CAMEL-3983:
--------------------------------------

Okay - that makes sense. So I will throw an exception is the message (body or at least one
header) is not serializable and no SPI implementation for a serializer has been provided.
Is there a common way to pass such a SPI implementation to the component. My first thought
was to pass it via URI properties... 

> 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