Camel 2.12.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.12.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
- Endpoint Annotations along with automatically created HTML documentation for the endpoint parameters; this makes it easier for component developers to add a few refactoring-safe annotations to their Endpoint or Consumer implementations and, (along with javadoc comments on the field or setter method), get nice user documentation on how to use the endpoint for free.
- ComponentConfiguration API provides a handy API for tools developers to introspect on a Component to find all the possible parameters, their types and any extra annotations (like Bean Validation Annotations) to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for configuring endpoints than just letting folks edit Strings.
- Spring Web Services now supports setting/receiving SOAP headers more easily using a header on the Camel Message.
- Evaluating Groovy expressions is faster as we cache the compiled scripts.
- Added
base64
option to Shiro Security to allow transferring security token over JMS and other transports as base64 encoded representation. - Made it easier to use Shiro Security as the credentials can be provided in headers, when sending a message to a secured route.
- Bindy now supports enums.
Fixed Issues
- Fixed setting .id in Java DSL on some EIPs such as the Validate
- Fixed Dead Letter Channel always handled exception, which wasn't the case if an Exception Clause was in use, which didn't had handled=true.
- Fixed Using PropertyPlaceholder in attributes defined on
<camelContext>
. - All Camel Components will configure their consumers when being created to ensure you can configure from URIs with
consumer.
as prefix. - Fixed QuickfixJEndpoint to adhere a given InOut MEP correctly.
- Fixed using property placeholders in a Simple predicate used inside a when in a Content Based Router when using Java DSL
New Enterprise Integration Patterns
New Components
camel-netty-http
- HTTP component using Netty as transport
New DSL
New Annotations
New Data Formats
New Languages
New Examples
New Tutorials
API breaking
Known Issues
Dependency Upgrades
- Commons Httpclient 4.2.3 to 4.2.5
- Commons Httpcore 4.2.3 to 4.2.4
- CXF 2.7.4 to 2.7.5
- EHCache 2.5.2 to 2.6.5
- Hibernate Validator 4.1.0 to 4.3.1
- JRuby 1.7.2 to 1.7.3
- Krati 0.4.8 to 0.4.9
- OpenJPA 2.2.1 to 2.2.2
- Spring 3.1.4.RELEASE to 3.2.2.RELEASE
- Spring Data Redis 1.0.3.RELEASE to 1.0.4.RELEASE
- Spring Security 3.1.3.RELEASE to 3.1.4.RELEASE
- Spring Web Services 2.1.2 to 2.1.3
- TestNG 6.8 to 6.8.5
- XStream 1.4.3 to 1.4.4
Changes that may affect end users
- The File and FTP consumers when using idempotent repository will no longer invoke
contains
with a directory name; this has been changed to only be checked for files. - Shutting down using Graceful Shutdown now requires the timeout value to be positive. And improved logic to avoid getting stuck in waiting for inflight messages, and having counter go negative.
Important changes to consider when upgrading
- Spring 3.0.x is no longer supported.
- The usage of the deprecated built-in
CommonsHttpMessageSender
has been replaced withHttpUrlConnectionMessageSender
by Spring Web Services. Consider this in case either thetimeout
orsslContextParameters
option is used through the Producer of this component. camel-scala-29
module has been removed.
Getting the Distributions
Binary Distributions
Description |
Download Link |
PGP Signature file of download |
---|---|---|
Windows Distribution |
||
Unix/Linux/Cygwin Distribution |
The above URLs use redirection
The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox
Source Distributions
Description |
Download Link |
PGP Signature file of download |
---|---|---|
Source for Windows |
Source for Unix/Linux/Cygwin |
Getting the Binaries using Maven 2
To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-core</artifactId> <version>2.12.0</version> </dependency>
SVN Tag Checkout
svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.12.0
Changelog
For a more detailed view of new features and bug fixes, see the: