[ 
https://issues.apache.org/jira/browse/CAMEL-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anbumani Balusamy updated CAMEL-8979:
-------------------------------------
    Attachment: camel-kafka.zip
                CAMEL-8979-src.txt
                CAMEL-8979-Kafka-Documentation.txt
                CAMEL-8979-camel-kafka-pom.txt

Hi Claus,  
                 Please find the attachment. Kindly note that we need to 
release this patches as new version so that it won't impact the existing Camel 
Kafka Integration projects.

-------------------------------------------------------------
Attached Files Detail 
-------------------------------------------------------------
CAMEL-8979-camel-kafka-pom.txt - Added new dependency
CAMEL-8979-src.txt - Code Changes to use the new KafkaProducer and 
ProducerRecord Classes
camel-kafka.zip - Code Fix src folder for your reference 
CAMEL-8979-Kafka-Documentation.txt - We can add this code sample/usage details 
to the Camel Kafka Component section (http://camel.apache.org/kafka.html).

Please let me know incase of any issues with the attachment.

Thanks!
Anbu




> Camel Kafka component is using Producer and KeyedMessage class
> --------------------------------------------------------------
>
>                 Key: CAMEL-8979
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8979
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-kafka
>            Reporter: Anbumani Balusamy
>            Priority: Minor
>         Attachments: CAMEL-8979-Kafka-Documentation.txt, 
> CAMEL-8979-camel-kafka-pom.txt, CAMEL-8979-src.txt, camel-kafka.zip
>
>
> Hi, I looked into the camel-kafka component version 2.15.2 and it's using old 
> Producer and KeyedMessage class for posting the message to kafka topic. From 
> 0.8.2 version we have new KafkaProducer and ProduceRecord classes. Can we 
> change the component to use the KafkaProducer and ProduceRecord classes?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to