Camel 2.5.0 release (currently in progress)

New and Noteworthy

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

• Added suspend/resume operations to CamelContext for warm restarts, or as the preferred way to temporary stop a running Camel application, and then later resume it. Those operations is also available in JMX.
• Improved management of routes in JMX. You can now suspend/resume routes which support suspension. There is a new removeRoute to remove a route from JMX. Routes with autoStartup=false is now also listed in JMX, to allow you to start the routes manually.
• The Asynchronous Routing Engine allows to be forced into synchronous mode for certain components, by specifying synchronous=true in the endpoint uri.
• FTP now supports MSV file systems. The ftp consumer will now traverse the directory structure using a cd <dir>, list files in cur dir pattern, as opposed to a list files <dir> style.
• Fixed issue with using multiple HTTP endpoints with the only difference being httpClient parameters.
• Fixed issue with Stream caching and deleting temporary files on Windows.
• Server thread pool settings can be configured on Jetty component.
• Easier to configure general HTTP/SSL socket connector properties on Jetty component.
• Fixed issue with sending an InOut message to Dead Letter Channel would cause Camel to expect a reply. Now the message will always be send to the DLQ as InOnly.
• Fixed issue when sending to a JMS destination, the option disableReplyTo was not used.
• Added two new functions to XPath to leverage Properties component and Simple language.
• Fixed issue when running Jetty server under heavy load throwing IllegalStateException
• JMS uses Asynchronous Routing Engine for Request Reply messaging over JMS.
• Fixed issue with a route could mistakenly pick up a route scoped OnException from another route.
• Fixed an issue with starting CamelContext after it had been shutdown, leading to routes not properly being re-initialized and started.
• The File and FTP consumers now support using preMove together with either noop or delete options.
• Added support for timeout in Recipient List, Splitter and Multicast EIPs when running in parallel mode.
• Added support for 3rd part UuidGenerator.
• Velocity can now find template files from filesystem/classpath when referring to them from other templates.
• Fixed issue with multiple CamelContext using same id being mixed as single CamelContext in JMX. Camel now fails to start if existing CamelContext already have been registered in the MBeanServer.
• The Message Filter EIP now stores a property on the Exchange to indicate if it was filtered or not.
• FTP supports sending site commands after successful login.
• Simple language can now compare numeric values which was entered as String types.
• Fixed limitation where PollEnrich could not poll from a file endpoint if the route started from a file endpoint as well.
• Fixed limitation with Simple language, before you could only use one and or or operator. Now you can use multiple operators in the same expression.
• Restlet component now supports using { } placeholders in uri, which gets replaced with headers from Exchange.
• Added dynamicRouter to the DSL to make it easier to do dynamic routing using a Bean to evaluate on-the-fly the next destination(s).
• Endpoint uris containing password is not logged in plaintext, but is now masked.

New Enterprise Integration Patterns

New Components

• Shiro Security
• Sip

New DSL

• Dynamic Router

New Annotations

New Data Formats

New Languages

New Examples

• camel-example-reportincident-ws-security-osgi

New Tutorials

API breaking

Known Issues

• The Tracer may not output all details for some situations such as when using onCompletion or intercept etc.
• Not all Examples have ANT build.xml files to run the example using ANT.

Important changes to consider when upgrading

• Support for JMS API 1.0.2 has been removed.
• The stopRoute method on CamelContext now leverages Graceful Shutdown when stopping. This is more intuitive to stop routes in a graceful and safe manner. You can the stop method with a timeout if you want to force stopping, which was the old behavior.
• The Web Console now requires JDK 1.6 as minimum to run.
• The artifacts camel-core-tests.jar and camel-spring-tests.jar has been deprecated and will be removed in a future release. You should always only use the camel-test.jar if you want to use the Camel Test Kit.
• Camel will now fail to startup if an existing CamelContext has been registered in JMX with the same id.
• If you did not set a id on <camelContext> it would have defaulted to camelContext. This has been changed to be the auto assigned name it's given by Camel, such as camel-1, camel-2 etc.
• Maven version 2.2.1 or better is now required to build Camel from source.
• If using Quartz with jobs persisted in a database, then mind that Camel now resolves job names based on endpoint uri, without parameters. This allows you to change cron parameters on the same job (reschedule jobs).
• The timeout option on Netty has been removed as it was flawed.
• Durable topic subscribers with JMS must now provide clientId, otherwise Camel will fail fast on startup.

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.5.0</version>
</dependency>

SVN Tag Checkout

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

Changelog

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

• release notes for 2.5.0