[
https://issues.apache.org/jira/browse/CAMEL-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958631#comment-13958631
]
Ioannis Polyzos edited comment on CAMEL-7339 at 4/3/14 8:53 AM:
----------------------------------------------------------------
The component already uses the DefaultExchangeHolder. This can be traced in
the serializeExchange method in the KafkaComponentUtil class.
The major change is that is not used in the form:
kafka:<servers>?zkConnect=<zookeeper>&topic=<topic>
But it is in the form:
kafka:<topic>?metadataBrokerList=<servers>& zkConnect=<zookeeper>
And this due i believe topic would serve better as the identifier of the
component instance.
was (Author: ipolyzos):
The component already uses the DefaultExchangeHolder. This can be traced in
the serializeExchange method in the KafkaComponentUtil class.
The major change is that is not used in the form:
kafka:<servers>?zkConnect=<zookeeper>&topic=<topic>
But it is in the form:
kafka:<topic>?metadataBrokerList=<servers>& zkConnect=<zookeeper>
And this due i believe topic should server better as the identifier of the
component instance.
> Transfer exchange in Camel-Kafka
> ---------------------------------
>
> Key: CAMEL-7339
> URL: https://issues.apache.org/jira/browse/CAMEL-7339
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Affects Versions: 2.13.0
> Reporter: Ioannis Polyzos
> Fix For: 2.14.0
>
> Attachments: camel-kafka.diff
>
>
> There is cases that need to transfer the whole exchange through kafka. I
> would like to share a patch for camel-kafka that support transfer exchange
> along with some more minor improvements such as more flexible configuration
> and default values preset.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
