[
https://issues.apache.org/activemq/browse/SMXCOMP-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SMXCOMP-725.
-------------------------------------
Resolution: Fixed
Fix Version/s: servicemix-camel-2010.01
Fixed in http://svn.apache.org/viewvc?view=revision&revision=922172
Thanks to Claus for providing the patch!
> servicemix-camel - Should preserve properties key case when copying from
> Camel to JBI
> -------------------------------------------------------------------------------------
>
> Key: SMXCOMP-725
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-725
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Reporter: Claus Ibsen
> Assignee: Gert Vanthienen
> Priority: Critical
> Fix For: servicemix-camel-2010.01
>
> Attachments: 725.txt
>
>
> When servicemix-camel JbiComponent is receiving reply from Camel, then it
> copies the Camel headers back as JBI Message properties.
> When it does that it uses wrong code for doing so.
> The 2 methods copyFromCamelToJbi should use EntrySet to walk a Map. This
> ensure you walk the map properly and that they keys case is preserved.
> The reason for this problem is that Camel leverages an CaseInsensitiveMap to
> ensure ease of use for end users, when working with HTTP headers as various
> products with HTTP can return headers in any kind of case. So we had issue
> with end user not being able to lookup Content-Type, content-type,
> Content-type and other cases this important header could be returned as.
> This class has the 2 methods which must be fixed
> https://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-camel/trunk/src/main/java/org/apache/servicemix/camel/JbiBinding.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
