Page History

...

• Camel has upgraded from Spring Boot v1 to v2 and therefore v1 is no longer supported. 
• Upgraded to Spring Framework 5. Camel should work with Spring 4.3.x as well, but going forward Spring 5.x will be the minimum Spring version in future releases. 
• Upgraded to Karaf 4.2. You may run Camel on Karaf 4.1 but we only officially support Karaf 4.2 in this release.
• Optimised using toD DSL to reuse endpoints and producers for components where its possible. For example HTTP based components will now reuse producer (http clients) with dynamic uris sending to the same host. See more details in the toD documentation.
• The File2 consumer with read-lock idempotent/idempotent-changed can now be configured to delay the release tasks to expand the window when a file is regarded as in-process, which is usable in active/active cluster settings with a shared idempotent repository to ensure other nodes dont too quickly see a processed file as a file they can process (only needed if you have readLockRemoveOnCommit=true).
• Allow to plugin a custom request/reply correlation id manager implementation on Netty4 producer in request/reply mode.
• The Twitter component now uses extended mode by default to support tweets > 140 characters
• Rest DSL producer now supports being configured in rest configuration via endpointProperties.
• The Kafka component now supports HeaderFilterStrategy to plugin custom implementations for controlling header mappings between Camel and Kafka messages.
• Rest DSL now supports client request validation to validate that Content-Type/Accept headers is possible for the rest service.
• Camel has now a Service Registry SPI which allow to register routes to a service registry such as consul, etcd, zookeeper using a Camel implementation or Spring Cloud
• The SEDA component now has a default queue size of 1000 instead of unlimited. 

And these important fixes:

...

New Enterprise Integration Patterns

New Components

• camel-as2 - Component used for transferring data secure and reliable over the internet using the AS2 protocol
• camel-mybatis - Now has a mybatis-bean component that supports using MyBatis annotations on POJO beans to specify the SQL queries and mappings.
• camel-web3j - The web3j component uses the Web3j client API and allows you to add/read nodes to/from a web3j compliant content repositories.

...

• Camel has upgraded from Spring Boot v1 to v2 and therefore v1 is no longer supported. Migrating from SB1 to SB2 may require changes, see the Spring Boot v1 to v2 migration documentation for details.
• Upgraded to Spring Framework v5 as default. Support for Spring Framework v4.3 is deprecated and not recommended to be used.
• Upgraded to Karaf 4.2. You may run Camel on Karaf 4.1 but we only officially support Karaf 4.2 in this release. 
• The camel-jms Maven pom.xml file now exclude spring-messaging dependency as this JAR is not used.
• Unit testing Camel with Spring Boot and extending the base classes CamelTestSupport or CamelSpringTestSupport is now throwing an exception as this has never been intended/support. Instead use the CamelSpringBootRunner JUnit runner, and do not extend a base class.
• The file consumer has changed to use readLock=none as default instead of readLock=markerFile. Documentation already indicated that readLock=none was the default.
• The SEDA component now has a default queue size of 1000 instead of unlimited. 

Getting the Distributions

...