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