Apache Camel celebrates 5 years in development with 2.10 release
The rule-based routing and mediation engine gets a big cloud-focused update in time for its fifth year in development.
Off the back of celebrating its fifth birthday at CamelOne 2012,
the Apache Camel team have put the finishing touches to their next
release, Apache Camel 2.10, adding in an array of new components to
the Apache enterprise application
No less than 483 issues have been resolved this time round, but
the real draw is the 18 components added to the package, including
Twitter, allowing for
deeper cohesive messaging for users. With the Twitter component,
based on the Twitter4J library, users may obtain direct,
polling, or event-driven consumption of timelines, users, trends,
and direct messages. An example of combining the two can be found
Other additions to the component catalogue
include support for HBase, CDI, MongoDB, Apache Avro,
DynamoDB on AWS, Google GSON and Guava. Java 7 support is much
more thorough now, as is support for Spring 3.1.x and Netty. A
full list of all resolved issues can be found here.
Apache Camel comprises a number of Apache projects such as
distributed ESB and JBI container Apache ServiceMix,
message broker ActiveMQ, JAX-RS supporter CXF, OSGI-based Karaf and
NIO Framework-focused Mina. It’s garnering plenty of
interest from vendors, all keen on bolstering their
middleware messaging offering for a cloud assault. The most notable
move thus far was
Red Hat’s acquisition of FuseSource last week, a key
contributor to Apache Camel over the years since their Software
Fellow, James Strachan founded the Camel project.
It’s been five hard years’ worth of toil though, with Apache
Camel 2.10 really showcasing what the open source project can do.
Since the first release on July 2nd 2007, 22 more have followed,
each making Camel that much better. The project has gone from
strength to strength over the years as the stats
suggest and it was made a Top Level Project at Apache in 2009.
Make sure you use the brand new version available here.