Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 570BB10E44 for ; Thu, 3 Apr 2014 06:55:22 +0000 (UTC) Received: (qmail 48504 invoked by uid 500); 3 Apr 2014 06:55:21 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 48410 invoked by uid 500); 3 Apr 2014 06:55:18 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 48363 invoked by uid 99); 3 Apr 2014 06:55:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 06:55:16 +0000 Date: Thu, 3 Apr 2014 06:55:16 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-7339) Transfer exchange in Camel-Kafka MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958579#comment-13958579 ] Claus Ibsen commented on CAMEL-7339: ------------------------------------ At first glance this patch seem to big and changes too much, We have some transferExchange logic from camel-core to serialize/de-serialize an exchange which we use for the components that support transferExchange option. The patch should reuse that logic. It's this class org.apache.camel.impl.DefaultExchangeHolder And you can find an examples used in these components ./camel-hawtdb/src/main/java/org/apache/camel/component/hawtdb/HawtDBCamelCodec.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-hazelcast/src/main/java/org/apache/camel/component/hazelcast/seda/HazelcastSedaConsumer.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-hazelcast/src/main/java/org/apache/camel/component/hazelcast/seda/HazelcastSedaProducer.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-jms/src/main/java/org/apache/camel/component/jms/JmsBinding.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-leveldb/src/main/java/org/apache/camel/component/leveldb/LevelDBCamelCodec.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-mina/src/main/java/org/apache/camel/component/mina/MinaPayloadHelper.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-mina2/src/main/java/org/apache/camel/component/mina2/Mina2PayloadHelper.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-netty/src/main/java/org/apache/camel/component/netty/NettyPayloadHelper.java:import org.apache.camel.impl.DefaultExchangeHolder; ./camel-sql/src/main/java/org/apache/camel/processor/aggregate/jdbc/JdbcCamelCodec.java:import org.apache.camel.impl.DefaultExchangeHolder; Maybe you can work on a patch that uses the current code base as-is, and adds support for transferExchange using the logic from camel-core. > 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)