Return-Path: 
 <users-return-44431-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
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 C3EA71010E
	for <apmail-camel-users-archive@www.apache.org>;
 Tue,  5 Nov 2013 15:55:01 +0000 (UTC)
Received: (qmail 17706 invoked by uid 500); 5 Nov 2013 15:54:58 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 17650 invoked by uid 500); 5 Nov 2013 15:54:54 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 17605 invoked by uid 99); 5 Nov 2013 15:54:49 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 15:54:49 +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 bobjolliffe@gmail.com
 designates 209.85.212.172 as permitted sender)
Received: from [209.85.212.172] (HELO mail-wi0-f172.google.com)
 (209.85.212.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 15:54:42 +0000
Received: by mail-wi0-f172.google.com with SMTP id ez12so2314582wid.11
        for <users@camel.apache.org>; Tue, 05 Nov 2013 07:54:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=NNhI489S+R/x3FKU66Yj4MTEV5Q3Lo7sbv3/zrmgjn4=;
        b=SjUJirUAjr4sxBxZ+zpzdYBfT6SU6LX+RSRdujhbnB5k8c73evtP4kndwDXASNACRu
         XuJrbts12wWOOIjIP1/qQ6SUCo0dbuZ9kQ8QtQbyUYOxhZgRMmMuncxgf3x/VLcsKA0N
         fHwpviFnIBPRIM7WEIyA9JO1qupJBNviV6JPt6FI+ItNXRQRSzPE190ByzfgP4bg1ers
         8DgGvsEUyKcbYe9SqqCnAvwcdSWrLlAwFQI8E9wMneSlSKXexWYvGelLtO3N6YT3w9M+
         JND+itOnuLzXr5r0qoXUpzQVndo0yEt15P3JItTMvcGkKSesBg6xUpms7PiCebbEzmIj
         oaXg==
MIME-Version: 1.0
X-Received: by 10.180.185.203 with SMTP id fe11mr17471630wic.29.1383666862408;
 Tue, 05 Nov 2013 07:54:22 -0800 (PST)
Received: by 10.194.36.231 with HTTP; Tue, 5 Nov 2013 07:54:22 -0800 (PST)
Date: Tue, 5 Nov 2013 15:54:22 +0000
Message-ID: 
 <CACd=f9fcMkERMt5a6Nw0_ou=dO75AzdO7ZSD_Rp5-kmHVQmSBA@mail.gmail.com>
Subject: Join after a split
From: Bob Jolliffe <bobjolliffe@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=001a11c340e2d24b1f04ea700bc1
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c340e2d24b1f04ea700bc1
Content-Type: text/plain; charset=ISO-8859-1

Hi

I have a route which takes a database query result set, splits it by row,
then proceses each row using another  route with seda endpoint.  Something
like:

<route id="synch-rm" autoStartup="true">
      <description>Get updates from dhis db and post to
registry</description>
      <to uri="sql:{{hmisdb.selectOus}}?dataSource=#dhisdb"/>

      <!-- process rows concurrently -->
      <split>
        <simple>${in.body}</simple>
        <to uri="seda:newFacility"/>
      </split>
   <log message="Done"/>
</route>

Is there I can cause the main thread in this route to wait until all the
seda:newFacility routes are complete before getting to the log message?

Bob

--001a11c340e2d24b1f04ea700bc1--