Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DFF45102EC for ; Wed, 10 Jul 2013 08:43:10 +0000 (UTC) Received: (qmail 15781 invoked by uid 500); 10 Jul 2013 08:43:08 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 15665 invoked by uid 500); 10 Jul 2013 08:43:08 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 15657 invoked by uid 99); 10 Jul 2013 08:43:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 08:43:07 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of robert@budzko.eu does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 08:43:01 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Uwpyy-0007Ch-Mh for users@camel.apache.org; Wed, 10 Jul 2013 01:42:40 -0700 Date: Wed, 10 Jul 2013 01:42:40 -0700 (PDT) From: solimo To: users@camel.apache.org Message-ID: <1373445760695-5735415.post@n5.nabble.com> In-Reply-To: References: <1373302919563-5735290.post@n5.nabble.com> Subject: Re: Enricher - coping strategy MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi! Claus Ibsen-2 wrote > This is working as designed. > > When using the enricher EIPs then the idea is that having the original > message and the new message to combine these into a original message > that is enriched with information from the new message. I see. Any idea how would you handle "expensive" message which we want to enrich :) ? Do not user enricher :)? Store expensive part in property? Reimplement message copy method? Tbh, those ideas sounds fishy to me. Robert -- View this message in context: http://camel.465427.n5.nabble.com/Enricher-coping-strategy-tp5735290p5735415.html Sent from the Camel - Users mailing list archive at Nabble.com.