[
https://issues.apache.org/activemq/browse/SMXCOMP-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SMXCOMP-639.
-------------------------------------
Resolution: Fixed
Fix Version/s: servicemix-camel-2009.02
Patch has been applied in
http://svn.apache.org/viewvc?view=rev&revision=822227, with a slight
refactoring to move the header strategy handling into the JbiBinding as
suggested by Willem.
Thanks to Willem and Dave for their input on this!
> Add support for header filter strategy to servicemix-camel jbi endpoints
> ------------------------------------------------------------------------
>
> Key: SMXCOMP-639
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-639
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.01
> Environment: Servicemix 4.x, All platforms
> Reporter: Dave Stanley
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2009.02
>
> Attachments: patch.txt
>
>
> As per [CAMEL-766|http://issues.apache.org/activemq/browse/CAMEL-766] camel
> supports a header filter strategy for controling how camel headers are
> propagated to various protocols. This improvement is to add support for the
> Camel HeaderFilterStrategy to servciemix-camel to allow more fine grained
> control over the message header properties.
> In particular this is useful when using a camel router to dynamically route
> messages to JBI endpoints. Assuming an InOut exchange, as the message comes
> back from the jbi endpoint, through the intermediate camel route, extra camel
> headers/message exchange properties are added to the jbi exchange before
> being passed back into the nmr. Using the filterStrategy you can control
> which camel headers propagate back and which ones don't.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
