The Apache Camel project celebrates the new 2.4.0 release. This release comes a bit earlier than the usual once a quarter release, but the quantity and quality of the issues resolved surely prompted it, most notably the async support, osgi related improvements and the move to spring 3.0.3. We are extremely grateful to the community for all the contributions.
The 2.4.0 release (see release notes for details) includes approx 182 issues resolved (new features, improvements and bug fixes) among which, in no particular order:
- Fully non blocking Asynchronous Routing Engine which all EIPs and some Camel Components supported.
- OSGi blueprint is now supported
- The camel-spring module now supports OSGi out of box.
- Spring 3.0.3 is now the default Spring version used by Camel.
- Added new
<contextScan>to scan the Registry for
RouteBuilderinstances, just as scanning the classpath etc.
- Manually started routes is now also Graceful shutdown by Camel
- Fixed issue using RouteContextRef with multiple CamelContext from the same Spring ApplicationContext.
- Spring Security is upgrade to spring security 3.0.3.RELEASE.
- Many fixes in components like Bindy, JMS, HTTP, FTP, Quartz, CSV
- Added a Debugger API to be leveraged by 3rd party tooling.
- Improvements for managing Camel using JMX.
- Upgraded to latest release of Scala 2.8.0RC7 in Scala DSL
- Introduced ProcessorFactory to be able to use a custom factory to be able to manipulate Processor creation process. For example to add additional outputs or manipulate the route model.
- Properties component can lookup
java.util.Propertiesfrom the Registry using the
Download Camel now and enjoy the ride!