Apache Camel 3.x Upgrade Guide
This document is for helping you upgrade your Apache Camel application from Camel 3.x to 3.y. For example if you are upgrading Camel 3.0 to 3.2, then you should follow the guides from both 3.0 to 3.1 and 3.1 to 3.2.
Upgrading Camel 3.4 to 3.5
FluentProducerTemplate
The template will now automatic clear its state send sending the message, this avoids end users having to call clearAll after usage,
in case the template should be reused to send other messages.
After the template has been started / used the first time, then its general configuration cannot be altered later, instead create a new template.
PackageScanClassResolver
The PackageScanClassResolver will now skip abstract classes in its findImplementations method.
camel-bean
The bean(class) EIP will now lookup in the registry first whether there is a single bean instance of the given class type
and use the existing bean (for singleton scope) instead of creating a new instance.
camel-cassandraql
Load-balancing policy has changed. There are no existing load balancing policies (see upgrade guide).
To customize load balancing policy, please use the parameter loadBalancingPolicyClass and provide own implementation
of load balancing policy.
Session impelentation class has changed from com.datastax.driver.core.Session to
com.datastax.oss.driver.api.core.CqlSession (see upgrade guide).
This could have direct impact on the type of parameter beanRef if you are using Provided Session reference.
There is a new parameter datacenter (with default value datacenter1). Data center has to be defined for the proper
behavior of the default load balancing policy.
camel-sjms
The default value for keepAliveDelay is changed from -1 to 5000 in the batch jms consumer.