Camel 2.6.0 release (currently in progress)

New and Noteworthy

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

• Fixed issue in OSGi with refreshing Camel bundles causing a race condition when discovering type converters
• Introduced ScheduledRoutePolicy with the Quartz component
• Java DSL RouteBuilder now fails if onException and the likes are not configured before routes, which they must.
• Easier to debug routes from camel-test using the Debugger
• Fixed problem installing camel-cxf feature on Apache Karaf.
• The EIP now supports property placeholders in the String based options (a few spots in Java DSL where its not possible). For example:

  <convertBodyTo type="String" charset="{{foo.myCharset}}"/>

• Introduced ScheduledRoutePolicy to allow you to schedule when routes should be active.
• Introduced stepwise option to FTP component to allow end users to control how to traverse directories of the FTP servers. This allows you to set stepwise=false to return back to the behavior from Camel 2.0 - 2.4. See more at the FTP documentation.
• Thread names now outputs CamelContext name which makes it easier to differentiate when running multiple Camel applications in the same JVM.
• Introduced contentCache option to XSLT component to allow easy reloading of stylesheets during development.
• Improved Camel JMX to always find next free name when registering in JMX and existing name exists (to remedy name clash). This makes it easier when deploying muliple WARs in the same JVM where the Camel applications may have same CamelContext id. In OSGi the name in JMX now has the bundle id as prefix.
• Fixed BeanShell language

New Enterprise Integration Patterns

New Components

• Spring Web Services
• JMX

New DSL

New Annotations

New Data Formats

• Syslog

New Languages

New Examples

New Tutorials

API breaking

• camel-test JAR in the CamelSpringTestSupport classes now returns a more generic AbstractApplicationContext type in the createApplicationContext method.

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.
• Project cannot be fully build using Maven 3.0
• One may encounter build errors in camel-ftp with java versions older than "1.5.0_24"
• Dozer does not work in OSGi
• camel-blueprint is not fully feature complete (such as @Producer, @Consume is not supported)
• camel-blueprint using <package> scan does not work

Important changes to consider when upgrading

• Upgraded to Spring 3.0.5
• Upgraded to Apache CXF 2.3.0 (although CXF 2.2.11 is still supported)
• Upgraded to Jetty 7.2.0.v20101020
• The Java DSL now enforces onException and the likes to be defined before routes, if not Camel will fail starting the route.

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

SVN Tag Checkout

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

Changelog

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

• release notes for 2.6.0