THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| style | padding-right:20px;float:left;margin-left:-20px; |
|---|
...
| style | min-height:200px |
|---|
...
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-google-mail-stream - The google-mail component provides access to Google Mail.
- camel-micrometer - To collect various metrics directly from Camel routes using the Micrometer library.
- camel-mybatis-bean - Performs a query, insert, update or delete in a relational database using MyBatis.
- camel-service - Represents an endpoint which only becomes active when the CamelClusterView has the leadership.
- 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-rxjava2 - RxJava2 based back-end for Camel’s reactive streams component
- camel-testcontainers - Camel support for testcontainers
- camel-testcontainers-spring - Camel unit testing with Spring and testcontainers
New DSL
New Annotations
New Data Formats
...
- 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.
- Unit testing Camel with Spring Boot and extending the base classes
CamelTestSupportorCamelSpringTestSupportis 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.
- Upgraded camel-bean-validator to Bean Validation API 2.0 (JSR 380 - Bean Validation 2.0) is part of JEE 8, and as therefore camel 2.22.0 may not be running on Java EE 7 server.
Getting the Distributions
...