[ 
https://issues.apache.org/jira/browse/CAMEL-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451546#comment-13451546
 ] 

Claus Ibsen commented on CAMEL-5581:
------------------------------------

We have 100+ components in Camel and none have this kind of custom strategy. I 
wonder why this is needed. Can you describe a use-case?

It seems to me you want to use the Content Enricher EIP instead? This EIP 
allows to enrich an existing Exchange with another Exchange.
http://camel.apache.org/content-enricher.html

For that there is the {{AggregationStrategy}} interface, where you can do 
custom coding.


                
> Add an ExchangeStrategy to the HBase Component.
> -----------------------------------------------
>
>                 Key: CAMEL-5581
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5581
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hbase
>    Affects Versions: 2.10.1, 2.11.0
>            Reporter: Claudio Corsi
>            Priority: Minor
>             Fix For: 2.11.0, 2.10.2
>
>         Attachments: hbase-exchange-strategy.patch
>
>
> The current hbase component does not provide the ability to forward of the 
> exchange information except for the associated hbase data.  
> This improvement adds the concept of an ExchangeStrategy that users can 
> extend and allow them to include information from the current exchange 
> in-coming message to the out-going message.
> I have a default implementation that does nothing that can be extended by a 
> user.  This default implementation can be extended in the future such that 
> users will then not be required to add missing methods.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to