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 raul@evosent.com designates
 209.85.192.176 as permitted sender)
MIME-Version: 1.0
From: Raul Kripalani <raul@evosent.com>
Date: Fri, 12 Jul 2013 00:59:00 +0100
Message-ID: 
 <CAKoNANvCR5YSG0eMG6=wPY5m4bc7s3oiZbnU0OjxpM5F3YfwCw@mail.gmail.com>
Subject: Camel toolbox for frequently used pieces of logic
To: "dev@camel.apache.org" <dev@camel.apache.org>
Content-Type: multipart/alternative; boundary=047d7b6d7d3ac2331104e1452e4b

--047d7b6d7d3ac2331104e1452e4b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi guys,

For a few months I've been wanting to build a set of utility classes with
the goal of providing a "toolbox" for commonly used AggregationStrategies,
OnPrepare processors, debug processors, etc.

Basically to make life easier for everyone. I feel there's too much
repeating that users can avoid if we provide certain basic uses cases out
of the box.

Moreover, newcomers find it hard to fully understand the role of properties
and headers for data pipelining inside routes. This toolbox can help settle
the concepts in common EIP scenarios.

So feel free to contribute your thoughts and ideas on
https://issues.apache.org/jira/browse/CAMEL-6542.

What pieces of logic do you tend to repeat across projects? What do you
carry in your Camel "toolbox" that other users may benefit from?

Thanks,

*Ra=FAl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

--047d7b6d7d3ac2331104e1452e4b--