Camel 2.16.0 release (currently in progress)

New and Noteworthy

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

Noteworthy improvements:

The route models (definition classes) preserve property placeholders, which allows round trip editing, and also prevents showing potential sensitive information
Added onPrepareFailure option to Dead Letter Ch annel to allow a custom processor to prepare the Exchange before sending to the dead letter queue.
MongoDB tailable consumers now allow setting the readPreference option.
Using setFaultBody / setFaultHeader behaves similar to setBody / setHeader to preserve existing headers/attachments by setting on existing IN or OUT message.
Java DSL using choice with end vs endChoice now validates you use them as intended. Any misconfiguration now throws an exception explaining the problem.
POJO Producing and POJO Consuming lifecycle is now in sync with CamelContext which ensures it works as similar to Camel Routes does. Also the created producer/consumer is stopped when Cam elContext is stopping to cleanup properly.
JMS component now allows configuring concurrentConsumers/maxConcurrentConsumers separately between from(jms) vs to(jms) using request/reply over JMS
Added SEARCH operation to Elasticsearch component
The Properties component (property placeholder) now supports an encoding option to allow reading the .properties files using a specific charset such as UTF-8. By default ISO-8859-1 is used (latin1)
Added receviveBufferSize option to the FTP component to make download faster. The size is by default 32kb buffer.
The Aggregator2 EIP now allows an external source usin g a AggregateController to control the aggregator, such as for forcing completing a group or all groups, or query runtime information from the aggregator. A default controller is provided out of the box if none has been configured.
The Aggregator2 now enlists in JMX using a ManagedAggregateProcessorMBean which has more information, and also allows using the aggregate controller to control it.
The Aggregator2 now includes more runtime statistics which can be accessed from Java and JMX about number of incoming and completed exchanges, and per different completion triggers.
The Aggregator2 now supports pre-completion mode if the aggregation strategy implements PreCompletionAwareAggregationStrategy. This supports the use-case w here an incoming Exchange are used to determine if the current aggregated group is completed or not. If completed the group is emitted as-is, and the new incoming Exchange is used to start a new group from scratch.
Added options to Mail consumer so it can skip or handle a mail message that cannot be read from the mail server in the batch; and then move on to read the next message. This ensures the consumer can deal with mail boxes that has problematic mails that otherwise will cause no mails to be retrieve by the consumer in the batch.
The runtime route processors and their corresponding model definition are now linked by their id using HasId, so its easier to obtain the processor or model definition from the getProcessor(id) and getProcessorDefintion(id) api on CamelContext.
CamelContext now also includes a getManagedProcessor API to easily get the mbean client api for the processor, so you can access the runtime JMX statistics from Java code.
Spring Boot applications now block the main thread of the execution
Spring Boot automagically loads XML routes definitions from classpath
Added MainListener to make it easier for Camel Boot / Standalone Camel to implement custom logic to trigger during the starting and stopping of the application.
Camel Jackson now provides Map to Object converter
Ability to refer to existing hazelcast instance by id, using Hazelcast Component
Direct and Direct-VM now supports the failIfNoConsumers option
Making it easier to add custom Type Converter to your Camel applications without having to use the META-INF file. In Spring or Blueprint just add them as <bean>s. See more details at Type Converter documentation.
camel-cxf PAYLOAD supports stream cache out of box.
BridgePropertyPlaceholderConfigurer supports to handle the jasypt encryption inside and outside of the camelContext.
The camel-aws component now support Amazon DynamoDB version 2
< /span>
The Wire Tap eip now also emits event notifications when sending the Exchange to the wire tap destination
Camel Test has new option isDumpRouteStats that dumps all route usage statistics as XML files in target/camel-route-stats directory, which can be used to inspect "route coverage" reports.
Now Camel Netty component doesn't intercept consumers with httpMethodRestrict=OPTIONS
Now Netty HTTP resolves OPTIONS prefix matches earlier
Using Load Balancer with Java DSL now builds the route model using the specific model types, which renders a more accurate route model
Enhanced the PredicateBuilder to support vargs and list in the "or" builder method
Using custom HttpBinding with HTTP and HTTP4 is now easier as they can be instantiated using a default no-arg constructor
Added readLock=idempotent to the File2 consumer which allows to reuse an idempotent repository as read-lock which enables Camel to run reliable in clustered mode, where each node competes for the same files from a shared file system. This requires that the idempotent repository supports clustering such as Hazelcast Component or Infinispan - or using the JDBC for a shared database table.
Camel RX now ensures that observe and subscribe are done within an unit of work to ensure on completions is executed, such as they are done when you use regular Camel routes.
The JMS component now includes the underlying javax.jms.Session instance on the Camel message which allows end users to easier to use client acknowledge mode, in case the client wants to use the session to call recover or rollback.
Added completionEager option to Idempotent Consumer to whether to complete the idempotent consumer eager or when the exchange is done.
Working with the Camel source code in Eclipse with m2eclipse plugin improved to avoid endless file changed detection and recompile the source.
Add option suppressExceptions to JSonPath which allows to ignore exceptions such as NoSuchPathException when the json payload does not contain the path defined in the json expression.

Fixed the following issues:

File language now properly s upports file extensions having double dots, such as .tar.gz
Fixed issue with doTry not stopping routing if a fault message was set using setFaultBody within the doTry.
Fixed Bean language to support end parenthesis in quoted string literals as part of method parameters, and not as end of method signature.
Fixed FTP2 using pollEnrich with disconnect=true and delete=true, would disconnect before deleting the file. Now we disconnect last.
Various EIPs such as Splitter, Recipient List, Multicast no longer reuse message id in their sub messages, but each sub message has its own unique message id (just as the exchange has).
Fixed an issue with the circuit breaker Load Balancer not honoring the half open after period after an error was detected.
Fixed FTP2 now calling disconnect if there was no messages to poll, even when disconnect=true configured.
Fixed Throttler using method call expression in XML DSL was not working
Fixed stopping a route may stop context scoped OnException that would otherwise send message to an endpoint, now been stopped and an IllegalStateException was thrown while handling the exception.
Fixed using a Load Balancer from a context scoped onException may double up its processors participating in the balancer per route in the context.
Fixed parallelAggregate on multicast/splitter/recipient list to use a thread pool for running concurrently.
Fixed Stream caching to not delete data that was spooled to disk before both exchanges are done routing.
Fixed DefaultErrorHandler to use 1 sec redelivery delay out of the box as the other error handlers does.
Fixed setting logExhaustedMessageHistory=true on Dead Letter Channel to log the message history. This option is by default false on DLC as it would be as before (not noisy).
Fixed double refresh of the parent Spring Boot Application Context
Fixed configuring endpoint uri's with primitive types when the value is looked up in the registry using #notation would not work.
Fixed using transacted in the Scala DSL

New Enterprise Integration Patterns

New Components

camel-paho - For MQTT messaging using Eclipse Paho client
camel-pdf - For creating PDF documents
camel-grape - allows you to fetch, load and manage additional jars when CamelContext is running.
camel-slack - allows you to connect to an instance of Slack and delivers a message contained in the message body via a pre established Slack incoming webhook.

New DSL

New Annotations

New Data Formats

camel-boon - For mapping POJO to/from json

New Languages

New Examples

New Tutorials

API breaking

org.apache.camel.mode.LoadBalancerDefinition no longer implements org.apache.camel.processor.loadbalancer.LoadBalancer which is the runtime processor (this was never intended).
The ref attribute on <loadBalance> has been removed, as it has been deprecated for a long time, and you should use a <customLoadBalancer> to refer to a custom load balancer.
The copy method on StreamCache now takes an Exchange as parameter.
Various APIs in camel-jms has been adjusted to support including the JMS session parameter - javax.jms.Session. Though these API changes are mostly internal facing, and we d o not expect end users problems.

Known Issues

Dependency upgrades

Amazon Web Service Java SDK from 1.8.9.1 to 1.9.38
Apache JClouds from 1.8.1 to 1.9.0
Apache Olingo Odata from 2.0.0 to 2.0.3
Apns from 0.2.3 to 1.0.0.Beta6
AspectJ from 1.6.2 to 1.8.5
Async-http-client from 1.9.8 to 1.9.17
Cassandra from 2.1.2 to 2.1.5
Cassandra Datastax Java Driver from 2.1.2 to 2.1.6
DNSJava from 2.1.6 to 2.1.7
Docker-java from 0.10.5 to 1.2.0
Dropbox core Java SDK from 1.7.6 to 1.7.7
Dropwizard Metrics from 3.1.0 to 3.1.2
Ehcache from 2.9.1 to 2.10.0
Facebook4j from 1.1.12 to 2.2.2
Freemarker from 2.3.21 to 2.3.22
Google App Engine from 1.8.3 to 1.9.19
Gson from 3.2 to 3.2.1
iCal4j from 1.5.0.2 to 1.6.0
Infinispan from 6.0.2.Final to 7.2.0.Final
Jackson2 from 2.4.3 to 2.5.1
Jboss Weld from 2.2.4.Final to 2.2.11.Final
Jsch from 0.1.51 to 0.1.52
Jsonpath from 1.2.0 to 2.0.0
Kafka from 0.8.1.1 to 0.8.2.0
LightCouch from 0.1.3 to 0.1.6
MongoDB Java Driver from 2.12.4 to 3.0.1
MongoDB test harness from 1.46.4 to 1.47.3
Mvel2 from 2.2.1.Final to 2.2.4.Final
OGNL from 3.0.8 to 3.0.11
OpenEJB from 4.6.0.2 to 4.7.1
OpenJPA from 2.3.0 to 2.4.0
Openshift Java Client 2.5.0.Final to 2.7.0.Final
PDFBox from 1.6.0 to 1.8.9
Restlet from 2.2.x to 2.3.1
SLF4J from 1.7.10 to 1.7.12
Snakeyaml from 1.14 to 1.15
Spring upgrades
Sshd from 0.13.0 to 0.14.0
TestNG from 6.8.8 to 6.8.21
Twitter4J from 4.0.2 to 4.0.3
XStream from 1.4.7 to 1.4.8

Important changes to consider when upgrading

The dumpRoutesAsXml operation now preserve property placeholder used in the route models.
Using setFaultBody / setFaultHeader behaves similar to setBody / setHeader to preserve existing headers/attachments by setting on existing IN or OUT message.
If using concurrent consumer on JMS endpoints for request/reply over JMS then you must use the new replyToConcurrentConsumers, replyToMaxConcurrentConsumers options to configure the values.
When the Aggregator2 is forced completed the exchange property Exchange.AGGREGATED_COMPLETED_BY value has been changed from "forceCompletion" to "force" so its named like the other completion triggers.
Removed unsupported modules camel-web and camel-web-standalone.
Removed unsupported camel:dot functionalit y from camel:run plugin.
Removed unsupported camel-archetype-scala-component from maven archetypes.
The Maven coordinate for linkedin and olingo2 components changed to be aligned like all the others having groupId as just org.apache.camel.
If using MongoDB component, the option invokeGetLastError doesn't exist anymore. The option invokeGetLastError instructs the MongoDB Java driver to invoke getLastError() after every call. In the 3.0.0 MongoDB driver implementation, the getLastError() method in WriteResult has been removed. So, if needed, use an acknowledged WriteConcern when executing the write operation and then verify the correctness of the operation with the method wasAcknowledged() of WriteResult.
The Jing component now uses jing as schema name in uris, instead of rng or rnc. Those names has been removed.

< h2 id="Camel2.16.0Release-GettingtheDistributions">Getting the Distributions

Binary Distributions

Description	Download Link	PGP Signature file of download
Windows Distribution	apache-camel-2.16.0.zip	apache-camel-2.16.0.zip.asc
Unix/Linux/Cygwin Distribution	apache-camel-2.16.0.tar.gz	apache-camel-2.16.0.tar.gz.asc

+