+1 Because we have users which are using the XML DSL and try to avoid writing Java code - for whatever reason. With this "toolbox" of common implementations of popular Camel interfaces/concepts, we serve their needs much better. E.g. some thing like the UseLatestAggregationStrategy [1].
[1] https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=camel-core/src/main/java/org/apache/camel/processor/aggregate/UseLatestAggregationStrategy.java;h=aee57720752153c2b50833be4a8e8c8fb52c7233;hb=HEAD Best, Christian ----------------- Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Fri, Jul 12, 2013 at 1:59 AM, Raul Kripalani <r...@evosent.com> wrote: > 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úl 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 >
