Page History

...

• MongoDB Java Driver from 2.12.4 to 23.130.0.
• Embed MongoDB test harness from 1.46.4 to 1.47.02.
• Jsonpath from 1.2.0 to 2.0.0
• Restlet from 2.2.x to 2.3.1
• Various Spring version upgrades.

• Jackson2 from 2.4.3 to 2.5.1

• Json-path library from 1.2.0 to 2.0.0

• Amazon Web Service Java SDK from 1.8.9.1 to 1.9.30
• Apache JClouds from 1.8.1 to 1.9.0
• Async-http-client from 1.9.8 to 1.9.17
• Freemarker from 2.3.21 to 2.3.22
• Cassandra Datastax Java Driver from 2.1.2 to 2.1.5. 
• Cassandra from 2.1.2 to 2.1.4.
• Dropbox core Java SDK from 1.7.6 to 1.7.7
• Facebook4j from 1.1.12 to 2.2.2
• LightCouch from 0.1.3 to 0.1.6
• Apache Kafka from version 0.8.1.1 to 0.8.2.0
• Apache PDFBox from version 1.6.0 to 1.8.9
• Twitter4J from version 4.0.2 to 4.0.3
• Dropwizard Metrics from 3.1.0 to 3.1.1
• Gson from version from 3.2 to 3.2.1
• Infinispan from version 6.0.2.Final to 7.1.1.Final
• Docker-java from version 0.10.5 to 1.2.0
• Ehcache from version 2.9.1 to 2.10.0

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 functionality 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.

Getting the Distributions

...