Hump day

Apache Camel tunes its core with new release

Lucy Carey

A souped-up version of the open-source integration framework is available for download now, complete with seventeen new components.

The community around open-source integration framework Apache Camel is a prolific little hub, and in the space of just four and a half months, has put together a shiny new release –  Apache Camel 2.12 – the 53rd Camel version to date.

On the menu for developers is a total of 17 new components, four new examples, and souped-up performance in simple or bean languages and general routing. More than three hundred JIRA tickets have been solved, and a lot of bug swatting and general fine tuning has taken place. Reflecting the hugely active community around the platform, around half of these  new components come courtesy of external contributors, and the rest from Camel team developers.

Fulltime Apache Camel committer Claus Ibsen notes in his blog that this is the first release where steps have been taken to “allow Camel components documentation in the source code which gets generated and included in the binaries.” He also writes that “a Camel component can offer endpoint completion which allows tooling to offer smart completion”, citing the hawtio web console as an example of the ways in which this enables functions like auto completion for JMS queue names, file directory names, bean names in the registry.

Another notable development is the effective displacement of the camel-seda by the camel-disruptor, which by utilising the LMAX Disruptor provides SEDA behaviour in Camel.

There have also been some tunings of the camel-core to improve usability. This includes a reduction of stack-frames during routing making logging Camel’s stack traces less clunky, and reducing the need for AsyncCallback callbacks during routing. Stream caching configuration has become more simple with StreamCachingStrategy, and New FlexibleAggregationStrategy now acts as, “a one-stop to perform typical aggregation strategy logic out-of-the-box: filtering results, storing them in properties, headers or bodies, as a list, casting results, etc.”

Finally, for camel’s increasingly sociable user base,  camel-yammer and camel-facebook have been added to help integrate applications with social network APIs. And those on the sales side will now be able to use camel-salesforce to write integration code for platform.

You can download Apache Camel 2.12 here

Inline Feedbacks
View all comments