Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 25 Jun 2011 15:53:47 +0000 (UTC)
From: "Ashwin Karpe (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1624530379.40579.1309017227450.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <519933619.69595.1307271527485.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CAMEL-4055) Hazelcast should use CamelCase keys
 for its headers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashwin Karpe resolved CAMEL-4055.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.9.0)
                   2.8.0

Patches and documentation have been updated. Marking the issue as resolved

> 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.8.0
>
>         Attachments: CAMEL-4055-updated.patch, 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