Camel 1.4.0 release
New and Noteworthy
Welcome to the 1.4.0 release which includes 261 new features, improvements and bug fixes such as...
- major improvements in JMS and Mail components
- major improvements in Camel JMX management (enabled by default)
- major improvements in Transactional Client. Bypassing Dead Letter Channel redelivery, letting the originator system handle this, resulting in the JMSMessage is rolled back to the JMS queue.
- attachment support for Message
- various improvements in CXF, File, FTP, Velocity, Stream, Atom and XMPP components
- various improvements in the Java and Spring DSL
- new transaction error handler, see Transactional Client
- introduced ExceptionPolicyStrategy as strategy for exception clause selection during error handling (much improved default strategy in Camel)
- intercept() default behavior changed (see section - important changes)
- 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
- introduced Debugger and Tracer interceptor to track how exchanges is routed
- 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
- overall improved wiki documentation
- improved javadoc for camel-core and camel-spring
- dependencies is now on the finer grained jars if applicable (e.g. Spring)
- WebSphere 6.1 support
- Flatpack for processing fixed width or delimited files or messages using the FlatPack library (work in progress)
- SpringIntegration for integration with Spring Integration
- Scala (work in progress, not fully feature complete)
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.
- The Tracer and Log can cause a NPE if the Message Body is
null. A workaround is to configure it with
Important changes to consider when upgrading
CamelTemplate marked as @deprecated
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.
After usage of the template, you must call
stop() to let it release any resources obtained. See this FAQ entry.
Bean component minor change
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.
Unit test kits
The unit test kits camel-core-tests.jar and camel-spring-tests.jar is no longer distributed with the binary distribution. These jars can be downloaded from maven repositories.
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.
Default behavior of intercept() changed
In Camel 1.4 the DSL for intercept() has changed its default behavior to proceed by default.
In Camel 1.3 you had to do this:
In Camel 1.4 the proceed is default:
And in Camel 1.3 stop was default:
In Camel 1.4 you have to explicit state the stop:
In the last two examples we want to filter out all orders by a test user. In Camel 1.4 we need to use the
stop() to stop the intercept chain from proceeding.
Camel is now more strict when it comes to validation of URI configuration. If a parameter name couldn't be resolved Camel will throw an Exception. In this regard the File component you must change the delay parameters to have the
delay should be
DeadLetterChannel is now disabled if in transacted mode. Use the new transaction error handler instread, see Transactional Client.
Getting the Distributions
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:
SVN Tag Checkout
For a more detailed view of new features and bug fixes, see: