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 7A51ED2E0 for ; Thu, 6 Dec 2012 17:44:56 +0000 (UTC) Received: (qmail 99875 invoked by uid 500); 6 Dec 2012 17:44:56 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 99840 invoked by uid 500); 6 Dec 2012 17:44:55 -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 99818 invoked by uid 99); 6 Dec 2012 17:44:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 17:44:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.215.45] (HELO mail-la0-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 17:44:47 +0000 Received: by mail-la0-f45.google.com with SMTP id p9so6213611laa.32 for ; Thu, 06 Dec 2012 09:44:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :x-gm-message-state; bh=p3/MRguEmuEm1B9VswpK/MPEFpuWx0rJ5Yh70798lJQ=; b=EmYedQuCEZ5SIG2Q63voqBIn5cZB1R5MIJg1CRwNRs71ZOivEukYXTUqxhnL3IcrL8 w7FxjcaL3/brszcXRa0R1kt3ZWbZdK7qE9VUQ4bR4Sz8tAUn6DrNZGvLqRRyPWEuKptR IMwLqX/H7Ta5MqC72ANyZyqQhSWnVLWsMvXmrPx1SZvTZGrjbW5qGJ3yoXhbhSaKONUB 5YPeu7uh6EOAqaEwSkyMkf/dCXVnNk1Nk8pB8bqhLIjymyJ4duz6xcxL4bVxekxiCYwF 2HDNBs0w5n0/y+xSTGwmEsEg+4vA9VYQuNjsIndasfZ73XDTvqYWo3w1bFEbDcXJUCO8 7GoQ== Received: by 10.152.114.100 with SMTP id jf4mr2583165lab.47.1354815866617; Thu, 06 Dec 2012 09:44:26 -0800 (PST) MIME-Version: 1.0 Sender: jcarman@carmanconsulting.com Received: by 10.112.43.73 with HTTP; Thu, 6 Dec 2012 09:44:06 -0800 (PST) In-Reply-To: References: From: James Carman Date: Thu, 6 Dec 2012 12:44:06 -0500 X-Google-Sender-Auth: YdwaGbkrjNPp-sQQk_ew0H_f-94 Message-ID: Subject: Re: Multicast or pipeline? Newbie question To: "users@camel.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQl6EPj5JYiJMNocfSJf0C8e9kAbcowouiUrUyCOUbqq9fZZfIHOaOWZRvKph1L9igQYxkFP X-Virus-Checked: Checked by ClamAV on apache.org I would say you don't need anything really special here. Something like this should suffice: from("jms:queue:input").beanRef("beanOne", "methodOne").beanRef("beanTwo", "methodTwo"); On Thu, Dec 6, 2012 at 10:58 AM, Mike Stroming wrote: > Hi all, > > Another newbie question, if you don't mind. > > I have two processes that need the same message as input. However, the > second process should only run based on successful output from the first > process. Would a multicast/pipeline make sense here or not? I don't need > either to get it to work, but I'm trying to follow some sort of Camel > standard. > > Msg enters queue > bean one > if bean one successful > bean two > > Thanks, > Mike