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 DBE491179D for ; Fri, 27 Jun 2014 17:47:29 +0000 (UTC) Received: (qmail 91889 invoked by uid 500); 27 Jun 2014 17:47:29 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 91836 invoked by uid 500); 27 Jun 2014 17:47:29 -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 91814 invoked by uid 99); 27 Jun 2014 17:47:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 17:47:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boards@gmail.com designates 209.85.219.45 as permitted sender) Received: from [209.85.219.45] (HELO mail-oa0-f45.google.com) (209.85.219.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 17:47:27 +0000 Received: by mail-oa0-f45.google.com with SMTP id o6so5958104oag.4 for ; Fri, 27 Jun 2014 10:47:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UE2lqFeMtEc5r0cZjToSA1qi1vaYRHelCtJUymumCfQ=; b=quLObWPgplnFgbsFBr1Fa3fE+aM8KGEMRmNRTQQtRNe2aX7DRJsWxNVDyZ6vx7LJB5 eEy1rBKsTe8Si0/C2/+4L5ja/w1IIrrr6mk+N+K9r4kRGSx3hMvW31gct7sWn3Y3zcqm c/DSs8Ud9maoySLbxMA27iwMyuokpqhpeDHpabQUkeGUwqVCArB1kgvVEId5yr3TgU+R Dkwy8FXrC/BQJuRdgpDjWAXVMxIwNBM6PTdQjBUQ7eNpwgUH0hm98PYOoesD5D8IXqbC pKial5/Ve/ieBMwn8TlHBR3X7AlmyueXk9UEyAEoi0YIyw4fhDyDQnIrHssjmOPULWkj EKhw== MIME-Version: 1.0 X-Received: by 10.182.245.164 with SMTP id xp4mr25161068obc.23.1403891222292; Fri, 27 Jun 2014 10:47:02 -0700 (PDT) Received: by 10.76.128.177 with HTTP; Fri, 27 Jun 2014 10:47:02 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 Jun 2014 12:47:02 -0500 Message-ID: Subject: Re: What's the point of the OUT message on an Exchange? From: Matt Sicker To: Camel Users Content-Type: multipart/alternative; boundary=001a11c2b2ee9bb2e204fcd4e560 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2b2ee9bb2e204fcd4e560 Content-Type: text/plain; charset=UTF-8 Thank you, that actually helped quite a bit! I see that using the in message is just more convenient than copying headers all the time for an InOut chain. On 27 June 2014 00:44, Claus Ibsen wrote: > Hi > > See this FAQ > http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html > > If you have a copy of the Camel in Action book, see page 66 for more > details as well. > > On Thu, Jun 26, 2014 at 10:44 PM, Matt Sicker wrote: > > I don't understand what the point of using the out message is. It doesn't > > copy headers. It doesn't signify the end of a route as far as I can tell. > > It's not used for a reply message. I don't think any of the official > Camel > > components even use the out message. What good is it for? > > > > In my own project, I've created a final processor that copies the in > > message to the out message and selectively fills in headers that were > > configured for that processor. I don't even know why I do this other than > > as a way to get rid of the myriad JMS headers that get passed around from > > using JMS (and occasionally rogue HTTP headers returned from a SOAP call > > somewhere). > > > > Are there any good resources or explanations as to the point of the out > > message? It seems to complicate things as it doesn't seem as though you > can > > send a dual-message of anything by using both the in and out messages. > > > > -- > > Matt Sicker > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cibsen@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8: http://fabric8.io/ > -- Matt Sicker --001a11c2b2ee9bb2e204fcd4e560--