Camel 2.2.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.2.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
- Routing Slip now breaks when an exception occurred
- MINA now supports easier configuration of multiple custom codecs, which is needed when working with SSL.
- Improved TransactionErrorHandler two fold by reducing complexity of internal logic in Camel when working with transactions. And added better support for using multiple transactions in multiple routes. See more at section Using multiple routes with different propagation behaviors at Transactional Client.
- Recipient List now supports
parallelProcessing
,stopOnException
and references forAggregationStrategy
and thread pools. This applies to the@RecipientList
annotation as well. - Cleanup of spring jar dependencies.
- File Language is now merged directly into Simple language which among others makes Content Based Router in Spring XML using file language syntax easier.
- HTTP is now using CamelContext Properties instead of System Properties to set the http proxy configuration.
- Fixed Camel Proxy throwing exception if
null
was returned. - Improved error handling with Recipient List and Multicast which now performs redelivery etc. on that output node instead of starting again from the scratch.
- SEDA now supports
multipleConsumers
which allows you to use it for pub-sub messaging where each consumer concurrently will receive a copy of the Exchange. This is done with the help from Multicast EIP. - DefaultErrorHandler will now log a log line at
ERROR
level in case an Exception was thrown which could not be redelivered either. This aid to see that an Exception occurred instead of relying on the client logging it. You can customize this behavior on the Error Handler. - Fixed
groupedExchange
not working properly on Aggregator. - Graceful Shutdown which ensures Camel now shutdown in a more reliable and graceful manner. This also works with in memory components such as SEDA.
- Added new
log
in the DSL for dynamic human readable log messages.
New Enterprise Integration Patterns
New Components
- camel-ftp now supports
FTPS
(FTP over SSL/TLS) - camel-smpp
New DSL
markRollbackOnlyLast
log
New Annotations
New Data Formats
New Languages
New Examples
API breaking
DefaultComponent
The methods DefaultComponent.resolveAndRemoveReferenceParameter
and DefaultComponent.resolveAndRemoveReferenceParameterList
have been changed to make the leading #
sign for bean references optional and to throw an IllegalArgumentException
if a referenced bean is not in the registry. For details see CAMEL-2248.
Exchange
The property Exchange.FILTETED
have been removed as part of CAMEL-2288.
ExceptionHandler
The class org.apache.camel.spi.ExceptionHandler
now have two additional methods which accepts more details when an Exception occurred such as a message and the current Exchange.
@EndpointInject
The name
attribute in @EndpointInject has been renamed to ref
to be consistent with the other annotations. Its a reference for an Endpoint to be looked up in the Registry.
Known Issues
See known issues from previous releases.
Important changes to consider when upgrading
Spring jar dependencies have been cut down in camel-core.
The pom.xml
file for camel-core have cut down number of spring jar dependencies to allow Camel to easily run without any Spring .jars at all. However this affects you if you use maven and use camel-core without camel-spring or spring at all. If you want to use JMX with Camel then you need to add the following 4 spring jars required: spring-core.jar, spring-beans.jar, spring-context.jar, spring-aop.jar
. With maven you only need to depend on spring-context
and spring-aop
as they will bring in the other two jars.
See also Camel JAR Dependencies and Camel JMX.
Using filter in Splitter
The filter
no long influence the split
and its AggregationStrategy
as it was just too confusing why it did that. See CAMEL-2288 for details.
camel-http and proxy
The HTTP component used to read Proxy settings directly from system properties. You should instead configure proxy wide information as properties to the CamelContext
instead. See HTTP for details.
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.2.0</version> </dependency>
SVN Tag Checkout
svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.2.0
Changelog
For a more detailed view of new features and bug fixes, see the:
TODO: Fix for 2.2.0