[
https://issues.apache.org/activemq/browse/CAMEL-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53551#action_53551
]
Claus Ibsen commented on CAMEL-1886:
------------------------------------
Hadrian I have now a solution using the KeyValuePair object as holder.
It works as well with the scripting engines when I go the extra mile and
_washes the KeyValuePair object away_ when they get hold on the headers.
The other solution that does *not* use KeyValuePair do not need to do this and
thus is more elegant. However it requires to keep booking of the lower case
keys -> original key in a 2nd internal map.
So in result we got 2 possible solutions
a) Use KeyValuePair holder objects (that holds original key and value)
b) Use internal 2nd map to keep booking of lower case key -> original key
I will attach new files with a and b code
> Lookup headers from a Camel Message should be case agnostic
> -----------------------------------------------------------
>
> Key: CAMEL-1886
> URL: https://issues.apache.org/activemq/browse/CAMEL-1886
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0-M3
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0, 2.1.0
>
> Attachments: CAMEL_1886.patch, CaseInsensitiveMap.java
>
>
> Today the case matter so: getHeader("Foo") and getHeader("foo") is not the
> same.
> And for some protocols the header case do not matter such as
> - http
> - mail
> etc.
> And who would in real life want to send 2 headers that are different only
> depending on the case
> - Foo=me
> - foo=you
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
