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

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

 Hi Claus.S , 

 I saw in your last patch that you introduce a new object called 
_HazelcastMessage_ that wraps the body and header of the exchange and send both 
of them through the wire. To my understanding this is the purpose of 
_DefaultExchangeHolder_ object (plus additional info of the exchange like fault 
headers etc) . 

 Is there any specific reason used a second object to wrap headers and body ?

 Also  according to the documentation in 
http://camel.apache.org/maven/camel-2.7.0/camel-core/apidocs/org/apache/camel/impl/DefaultExchangeHolder.html
 , either the whole exchange should be transferred (transferExchange=true) or 
just the body of the message (normal usage).
 
 Please excuse me if my understanding is not correct, though I believe that it 
would be better to comply with this and in case of normal use 
(transferExchange=false) only the body should be send and no other 
information...

> 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.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

Reply via email to