A new release of Apache Camel [1] is out after a bit over 3 months of hard
work. Our thanks and gratitude go to the vibrant and growing community and all
the contributors who made Camel a stable, mature and production ready project.
Special thanks go to the many other projects, open source or not, who chose
Camel for their integration needs.
The Camel 2.3.0 release [2] (see release notes [3]) features some 276 issues
resolved. Most notable (in no particular order) are:
• Overhauled threading model and introducing threadPoolProfile to
define profiles for thread pools to have easy configuration.
• Improved the Failover load balancer to support round robin mode and a
few other options as well.
• Fixed issue with Camel not being able to run deployed as a WAR in
WebLogic server.
• Total overhaul of the Aggregator EIP, which now has better completion
triggers, and supports pluggable repository. For example to use camel-hawtdb as
persistent store. Also added support for recovery and transactional behavior
when using camel-hawtdb.
• Graceful Shutdown now shut down routes in the reverse order in which
they was started. Option shutdownRoutesInReverseOrder can be used to control
this behavior.
• Added ExchangeSentEvent to EventNotifier which contains time taken
and is emitted when an Exchange is sent to an Endpoint. This allows end users
to easily gather performance stats for Exchange send to endpoints.
• Simple and Bean languages now has a build in OGNL notation which
allows you to reference from Map or List structures and as well to invoke
methods in a OGNL like notation. See more details at Simple wiki page.
• camel-jetty supports the multipart/form post out of box.
• Property placeholders in for example endpoint uris is not natively
supported in camel-core which means you no long need to use Spring for that. It
works therefore in any environment as its provided out of the box in camel-core.
• Added org.apache.camel.builder.ProxyBuilder to easier create Camel
Proxy in Java / Java DSL.
• ProducerTemplate and ConsumerTemplate can now be configured with a
maximumCacheSize to control how many producers/consumers they can cache.
• Reduced registering producers in JMX to prevent using too much memory
and potentially registering short lived producers which didn't bring much value
of being managed as well.
• Now camel provides a karaf feature file with Spring 3.0.2.RELEASE,
the features url is
"mvn:org.apache.camel.karaf/apache-camel/2.3.0/xml/features-spring3"
• ... and much, much more....
Also notable is the number of new components added to this release:
• camel-nagios for sending passive checks to Nagios
• properties for using property placeholders to resolve endpoint uris.
• camel-gae extensions
• gauth component for implementing OAuth consumers.
• glogin component for programmatic login to Google App Engine
applications from Java clients.
• camel-hawtdb as persistent store for the Aggregator EIP.
• camel-netty for working with TCP and UDP protocols using Java NIO
based capabilities offered by the JBoss Netty.
• camel-scalate for working with the ScalaTE template framework
• camel-exec for executing system commands
• camel-bean-validator performs bean validation of the message body
using the Java Bean Validation API (JSR 303).
• camel-spring-security support to integrate the spring security with
Camel.
• camel-crypto using Camel cryptographic endpoints and Java's
Cryptographic extension it is easy to create Digital Signatures for Exchanges.
• camel-eclipse for using Camel with Eclipse RCP.
As usual, a lot of fixes and enhancement of the 90+ Components
Download [4] Camel now and enjoy the ride!
The Camel Riders
[1] http://camel.apache.org/
[2] http://camel.apache.org/2010/05/26/camel-230-released.html
[3] http://camel.apache.org/camel-230-release.html
[4] http://camel.apache.org/download.html
