Camel 1.4.0 release
New and Noteworthy
Welcome to the 1.4.0 release which includes: 192 tickets resolved (new features, improvements and bug fixes such as...)
- major improvements in JMS and Mail components
- JMS headers now preserve packagename style headers so Bean and [File] headers is preserved, so you can safely send the filename or bean method to invoke over the JMS wire.
- major improvements in Camel JMX management (enabled by default)
- Transactional Client improvements. Bypassing [DeadLetterChannel] redelivery, letting the originator system handle this. Meaning that a JMSMessage is rolled back to the JMS queue etc.
- various improvements in CXF, [File], FTP, Velocity, Stream components
- various improvements in the Java and Spring DSL
- refinements to run in OSGi containers
- some internal refactorings of package structure to avoid cycle dependencies
- @deprecated some core classes, that will be removed in Camel 2.0
- improved feedback for misconfiguration of camel routes such as mistypes of parameters
- introduced ExceptionPolicyStrategy as strategy for exception clause selection during error handling (much improved default strategy in Camel)
- overall improved wiki documentation
- improved javadoc for camel-core
- attachment support for Message
- introduced Debugger and Tracer interceptor to track how exchanges is routed.
- dependencies is now on the finer grained jars if applicable (e.g. Spring)
New Components
- SpringIntegration for integration with Spring Integration
New Data Formats
- None
New Languages
- [Scala] (work in progress, not fully feature complete)
New Enterprise Integration Patterns
- None
New Examples
- ANT build files for running the examples
- camel-example-loan-broker
- camel-example-spring-jms
API breakings
Potentially there can be an API breaking when upgrading from Camel 1.3 or older. We are sorry for this and will try to refrain from such API breakings in the future Camel 1.x releases. An API overhaul is scheduled for Camel 2.0.
Known Issues
CamelTemplate has been marked as @deprecated and you should use ProducerTemplate instead.
From Camel 1.4.0 on the ProducerTemplate must be retrieved from the CamelContext. You can then use it the same way as before.
ProducerTemplate camelTemplate = camelContext.createProducerTemplate();
Bean component sets a reference to the bean that is being invoked as a property on the Exchange. This property has change its key from "CamelBean" to "org.apache.camel.bean.BeanHolder" and the type is now a BeanHolder.
Camel deployed as a web application in WebSphere 6.1 can not discover annotated converters.
Important changes to consider when upgrading
In Camel 1.4 the Camel JMX agent has been enabled by default. To disable it, as the default in previous versions, you have to explicitly disable it. See the Camel JMX documentation 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>1.4.0</version> </dependency>
SVN Tag Checkout
svn co https://svn.apache.org/repos/asf/activemq/camel/tags/camel-1.4.0
Changelog
For a more detailed view of new features and bug fixes, see the release notes