Camel 2.15.0 release (currently in progress)

New and Noteworthy

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

• Component documentation now included in the built component JARs. And Java API and JMX API to access that documentation. And APIs to explain an endpoint uri and what all those configured options mean. 
• Component can now have associated label(s) which are used for grouping components into: core, database, messaging, http, rest, etc.
• Provide Configurer for user to configure the CXF conduit and CXF destination from Java code
• Added a DelegateEndpoint interface into Camel API
• Support to setup the SslContextParameters in the camel-restlet component
• Java DSL - Should support nested choice in doTry .. doCatch
• MongoDb component now stores OIDs of the inserted records in the message header
• Recipient List now supports specifying custom Exchange Pattern in the endpoint ur's
• Type Converter to enum's is now case insensitive, so you can convert safely level=info to an enum with name Level.INFO etc.
• XSLT and Validation components now provides all their endpoint configurations in the endpoint, and not only in the component, making these components like any other components.
• Made the Camel Karaf Commands reusable by moving common code into a camel-commands-core module that SPI can extend and plugin Camel commands for other environments.
• Further hardening of the SJMS component.
• Rest DSL with embedded routes now supports onException, intercept etc in use for those embedded routes, just like any regular routes. 
• Rest DSL now by default uses custom error message as-is without attempting to binding output (requires a HTTP error code of 300+ is set as a header)
• Camel Using PropertyPlaceholder now supports specifying a default value together with the key to lookup.
• Camel Using PropertyPlaceholder now supports not having to define a PropertiesComponent if all the placeholder keys has default values which are to be used (less configuration needed in those situations).
• Camel Using PropertyPlaceholder now supports 3rd party functions to lookup the property values, this allow end users to implement their own logic - we provide 3 out of the box functions to lookup values from OS environment variable, JVM system properties, or the service name idiom.
• RabbitMQ now pools Channels for the producer to avoid sharing same Channel among concurrent producers which are not recommended by RabbitMQ client.
• Camel commands is now reusable outside Apache Karaf as a base by the commands-core module.
• Camel commands using Jolokia for remote communication by the commands-jolokia module.
• More minor processors such as setHeader, removeHeader, removeHeaders and ditto for properties is now also enlisted in JMX under processors.
• Optimized usage of type conversion during routing reducing the number of attempts needed.
• Asynchronous routing engine that are forced to block threads now exposes this using a manager that offers runtime insight using JMX. And as well attempts to free blocked threads during graceful shutdown, to avoid any threads hanging in the JVM.
• Swagger now supports any kind of runtime environment, as only JMX being enabled is required.

Fixed issues

• Fixed processors was not enlisted in JMX when routes was transacted.
• Fixed the NullPointerException when using CXF endpoint with enrich
• Fixed the endpointProperty of restConfiguration doesn't work issue
• Fixed the issue that CircuitBreakerLoadBalancer fails on async processors
• Fixed MyBatis consumer ignoring maxMessagesPerPoll option
• Fixed potential issue with pollEnrich not triggering error handler if an exception was thrown in the polling.
• Fixed a memory leak if using Dynamic Router that loops many times, and uses any of convertBodyTo or setBody or transform in the loop, causing memory to stack up until the Exchange is done.
• Fixed and improved how Bean component and Simple language invoking beans detect methods that are overridden, and able to filter and apply this as a single method, to be invoked. Avoids AmbiguousMethodCallException being thrown.
• Fixed a thread leak if restarting routes using stop/start and the routes is a scheduled poll consumer, such as file/ftp components.
  
  

New Enterprise Integration Patterns

New Components

• camel-beanstalk - for working with Amazon Beanstalk jobs.
• came-cassandraql - Cassandra CQL3 support
• camel-chunk - for templating with Chunk engine.
• camel-docker - to communicate with Docker.
• camel-github - for integrating with github
• camel-google-calendar - provides access to Google Calendar via the Google Calendar Web APIs.
• camel-google-mail - provides access to Gmail via the Google Mail Web APIs.
• camel-pgevent - Component for sending/receiving notifications in PostgreSQL via the pgjdbc-ng driver
• camel-jira - for integrating with JIRA issue tracker
• camel-scr - for using Camel with SCR (OSGi declarative services) on OSGi containers such as Apache Karaf
• camel-spring-boot - for using Camel with Spring Boot
• camel-test-spring40 - for testing with Spring 4.0.x. camel-test-spring is for Spring 4.1.x onwards.

New DSL

• Added removeProperties to remove the properties from exchange.

New Annotations

New Data Formats

• camel-univocity-parsers

New Languages

New Examples

New Tutorials

Known Issues

Dependency Upgrades

• AWS-Java-SDK 1.8.3 to 1.8.9.1
• Codahale Metrics 3.0 to 3.1
• Guava 17.0 to 18.0
• Jsch 0.1.50 to 0.1.51
• Spring 4.0.7.RELEASE to 4.1.3.RELEASE
• Spring Security 3.1.7.RELEASE to 3.2.5.RELEASE
• RX Java 0.20 to 1.0.2
• ... and many other upgrades

Important changes to consider when upgrading

• Spring 4.1.x is now the default out of the box Spring version.
• Unit testing with Spring 4.0.x requires using camel-test-spring40, as camel-test-spring is for Spring 4.1 or better.
• Remember to add @BootstrapWith(CamelTestContextBootstrapper.class) if upgrading from Spring 3.x or 4.0.x to Spring 4.1 onwards, and using the camel-test-spring module.
• XSLT component now require configuring transformerFactory using URIs with the #syntax to refer to a bean. Just like any other component would do.
• Slight refactor in camel-metrics component which may affect users who are using the java endpoint types instead of configuring using uris
• camel-csv upgraded to Commons CSV 1.x which has a different API than the old 0.x version. End users may need to adjust their code.
• camel-sjms has been refactored a bit to further harden this component. End users may need to adjust their code.
• The simple function properties:locations:key has been renamed to properties-location:locations:key, as it would clash with the new functionality to specify a default value after the key name, eg properties:key:default
• Support for Jetty 8.x is deprecated and being considered to be dropped in next release (as Jetty 8 is EOL).
• Removed the backlog tracer commands from the Karaf Camel commands as they are not suitable for a CLI environment
• The need for runtime specific servlets in Swagger has been removed, and instead just use the default servlet which is provided out of the box. 

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

Changelog

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

• release notes for 2.15.0