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-4055) Hazelcast should use CamelCase keys for its headers
Date Thu, 23 Jun 2011 15:45:48 GMT

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

Ioannis Polyzos commented on CAMEL-4055:
----------------------------------------

 Claus sorry for the misunderstanding, my fault, I thought it was just camel case, I didn't
catch that should start with "Camel"...

 Ashwin thank alot for your help, please let me know if your like me to proceed with any further
changes ... 

> 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

        

Mime
View raw message