Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
Date: Thu, 24 May 2012 15:22:08 +0200
Message-ID: 
 <CALvzYd8_r1t2S4ub9MhC2upfCo70kkibPAEjyuPUTPSWcshQ3g@mail.gmail.com>
Subject: Use Camel to implement batches which are scheduled by a standalone
 scheduler
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: jb@nanthrax.net, dev@camel.apache.org
Content-Type: multipart/alternative; boundary=485b397dcd3984ddff04c0c82386

--485b397dcd3984ddff04c0c82386
Content-Type: text/plain; charset=ISO-8859-1

As you may know, JB wrote already a similar blog about this topic [1].
However, in my company we have a few additional and slightly different
requirements:
- The controller route has to respond with a return value which indicates
whether the exchange(s) could process without an error (return code == 0).
This means if the exchange is sent to an queue and another route consumes
this queue, we have to wait for this until we are able to provide a return
value.
- We have a more complex logic when we have to stop the route (e.g. we are
also consuming from a queue and want to stop the route when the queue is
empty)

I made already a few test by using a RoutePolicy, but without a solution
until now. If I finish this work, I will provide a new example for batch
processing in Camel.

[1]
http://blog.nanthrax.net/2011/08/use-camel-cxf-and-karaf-to-implement-batches/

Best,
Christian

--485b397dcd3984ddff04c0c82386--