You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Ioannis Polyzos (JIRA)" <ji...@apache.org> on 2011/06/06 22:14:59 UTC
[jira] [Issue Comment Edited] (CAMEL-4055) Hazelcast should use
CamelCase keys for its headers
[ https://issues.apache.org/jira/browse/CAMEL-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045062#comment-13045062 ]
Ioannis Polyzos edited comment on CAMEL-4055 at 6/6/11 8:13 PM:
----------------------------------------------------------------
I have uploaded a patch containing the aforementioned changes for your consideration.
Names changed to camel case to comply with the idiom you previously mentioned. Regarding the removal of control headers i.e operation type and object id, are already removed during the copyHeaders() call for Queue, Map, MultiMap, List and AtomicNumbers. In SEDA component these headers kept only in case transferExchange is set to true.
was (Author: omicron):
I have uploaded a patch containing the aforementioned changes for your consideration.
Names changed to camel case to comply with the idiom you previously mentioned. Regarding the removal of control headers i.e operation type and object id, are already already removed during the copyHeaders() call for Queue, Map, MultiMap, List and AtomicNumbers. In SEDA component these headers kept only in case transferExchange is set to true.
> Hazelcast should use CamelCase keys for its headers
> ---------------------------------------------------
>
> Key: CAMEL-4055
> URL: https://issues.apache.org/jira/browse/CAMEL-4055
> Project: Camel
> Issue Type: Improvement
> Components: camel-hazelcast
> Affects Versions: 2.7.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4055.patch
>
>
> Its an idiom that Camel components that supports headers to control its actions should use CamelCase for its keys, eg CamelHazelcastOperation.
> Also it would be great that if camel-hazelcast would remove the control headers after usage, eg operation type and objectId. Then those headers is not propagated during route as they was only intended as input for the hazelcast endpoint.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira