Camel 2.8.0 release (currently in progress)

New and Noteworthy

Welcome to the 2.8.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

• Fixed the OGNL support of Simple language to support dots in key for map access.
• You can now specify type parameters in Bean to exact select method to be used when having overloaded methods (overloaded methods have same name, but vary in parameter types).
• The SFTP component now allows you to customize keep alive settings.
• Fixed issue if explict setting JmsMessage body to null would cause Camel to re-initialize the body from the underlying javax.jms.Message on access again.
• Mock endpoints is now lenient, which means its easier to replace components with Mock for testing purposes. Using uri parameters which the Mock endpoint wont no longer complain about being unknown parameters.
• Camel places a breadcrumb header in the Camel Message which allow us to keep track of messages across transports such as JMS, HTTP and many others. See more details at MDC logging.
• Improved XPath to allow GC to kick-in a bit earlier to free memory as Camel will clear references to used Exchanges used during XPath evaluations.
• Fixed an issue using FTP endpoints with the interceptSendToEndpoint
• Camel Proxy supports asynchronous invocations using Future handles.
• The endpoint cache can be configured on CamelContext.
• Cometd supports custom security policy and extensions as documented here
• Caches such as ProducerCache and EndpointRegistry can now be purged from JMX.
• Added stats for number of redeliveries and handled failures to JMX.
• Added support for JBoss 6.
• JMS consumer uses CACHE_AUTO for default cache level. This ensure that it will automatic detect if its transacted and use CACHE_NONE which must be used for transacted. And CACHE_CONSUMER for non transacted.
• Improved Splitter in parallel mode to be more responsive when aggregating on-the-fly under high load, and reducing number of threads in-use.
• Added onPrepare to Multicast, Splitter and Recipient List to execute custom logic when preparing messages. For example you can use that to deep clone message bodies, or enrich messages before they are processed.
• Added CamelSqlQuery header to SQL Component to specify (per exchange) SQL query.
• camel-cache now works in OSGi.
• Fixed an issue with HawtDB file store growing to large.

New Enterprise Integration Patterns

New Components

• AWS-SNS
• AWS-S3
• TestNG

New DSL

• Wire Tap has now fluent builders in Java DSL to make it easier to configure.
• Added skipDuplicate option to Idempotent Consumer EIP to allow end users to handle duplicate messages more easily in Camel routes.

New Annotations

New Data Formats

New Languages

New Examples

• CXF Example OSGi

New Tutorials

API breaking

• Added purge method to ServicePool
• If you use Wire Tap from within a Content Based Router in Java DSL, then you need to use end() to indicate the end of the Wire Tap. See this test
• WireTapDefinition no longer extends from SendDefinition

Known Issues

Important changes to consider when upgrading

• Upgraded to slf4j 1.6.1

Getting the Distributions

Binary Distributions

Source 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:

<dependency>
  <groupId>org.apache.camel</groupId>
  <artifactId>camel-core</artifactId>
  <version>2.8.0</version>
</dependency>

SVN Tag Checkout

svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.8.0

Changelog

For a more detailed view of new features and bug fixes, see the:

• release notes for 2.8.0