[
https://issues.apache.org/jira/browse/CAMEL-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053922#comment-13053922
]
Ashwin Karpe edited comment on CAMEL-4055 at 6/23/11 3:34 PM:
--------------------------------------------------------------
I looked at the submitted patch and everything looks good. The patch has now
been committed to the codestream as revision "r1138929"
Ioannis, Thanks for your submission.
Cheers,
Ashwin...
was (Author: akarpe):
I looked at the submitted patch and everything looks good. The patch has
been committed to the codestram as revision "r1138929"
Ioannis, Thanks for your submission.
Cheers,
Ashwin...
Ashwin...
> 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
