Now that Apache Camel 2.19.0 has been released, let's summarize the features of interest. http://camel.apache.org/camel-2190-release.html
Apache Camel is a lightweight and highly functional integration framework. It's written in Java, but should work on other JVM languages such as Scala, Kotlin, and Clojure.
--You can connect to various external services and interfaces using more than 200 components provided by default. --Java / XML DSL with Enterprise Integration Patterns (EIP) (http://www.enterpriseintegrationpatterns.com/patterns/messaging/toc.html) fully implemented for clean routing of external I / O messages it can. --For programmatic use as a single JAR library, for use as a core routing engine for full-stack ESB servers such as JBoss Fuse Can be widely used. --Supports Spring Boot and can be used as a microservice on the cloud.
The main feature is Camel Connector Introduction. Since there are many other added functions, the details are omitted and only the notable ones are listed below. (For those who want to see everything, see here.)
--The new Camel Connector has been introduced. Connector is a one that narrows down the use cases rather than Component so that it can be immediately linked with an external system. Citizen integrators (a.k.a. iPaaS users) who are not full-fledged integration engineers aim to easily form inter-system cooperation.
for autoconfiguration. This allows you to disable Camel Spring Boot autoconfiguration by excluding ʻorg.apache.camel.springboot.CamelAutoConfiguration in your unit tests.
--Tool system
--Added camel: validate goal to Camel Maven Plugin. You can validate Java / XML root DSLs at compile time.
--Camel Main, Spring Boot, and Camel Maven Plugin now automatically shut down the JVM. The stop condition can be set to elapse of a certain time, end of processing all messages, and a certain idle time.
--Camel Maven Plugin can now perform live reload from XML DSL. Live reload can also be set from the Main class.
--Support for the OWASP dependency check Maven plugin.
--Further deprecation of deprecated components and camel-core API in Camel 3.0.
--Camel source code can now be built in Java 9.
--Introduced ReloadStrategy SPI. This allows the custom provider to initiate a live reload of the route.
--Camel Catalog's support for custom runtime providers that only support specific components, languages, and data formats. See camel-catalog-provider-karaf (Karaf) and camel-catalog-provider-springboot (Spring Boot) for samples.
--If Failover Load Balancer is set to ʻinheritErrorHandler = false, Camel's Error Handler will now be executed after the load balancer is exhausted. --Camel root XML dump now includes custom namespaces in xpathnotation. Similarly, editing an XML Camel root adds a namespace in thexpathnotation. --AddedRouteIdFactory. You can use RouteIdFactory to automatically set the route ID to a more meaningful name than route1, route2. --Added skipfunction to Simple language. --Upgrade to Jetty 9.3. (Jetty 9.2 will continue to be supported for Karaf 4.0.x users.) --Since the sample summary is generated from the source code, you can always check the latest status. https://github.com/apache/camel/tree/master/examples#examples --Introduced declarative Transformer and Validator based on data types. Seecamel-example-transformer-blueprint, camel-example-transformer-cdi, camel-example-transformer-demo, camel-example-validator-spring-boot` for usage samples.--Bean component
--When calling a method that returns a Callable instance, the method of that Callable is also called. As a result, Groovy functions / closures can be called.
--Salesforce component
--Support for the limits, recent items, ʻapprovalsandcomposite APIs. --NATS component --Support for TLS and automatic connection flash. --Metrics component --Gauge type support. --File component --Support for clustering read-lock strategies with ʻidempotent-changed or ʻidempotent-rename. --CDI component - RouteBuilder auto-configuration can now be disabled from Camel CDI configuration - Camel contexts automatic start can now be disabled from Camel CDI configuration - Camel CDI now provides support for TransactionErrorHandler and TransactionPolicy via JTA --Kafka component --Saved the offset state offline (stateRepository) so that you can resume from the previous offset. --Improved to make it easier to set / use components. --Introduction of topic-based idempotent repositories by Kafka for Idempotent Consumer EIP. --Changed to automatically convert the message body when sending a message (default serializer is String). Also, key and partitionKey can now be specified in the endpoint URI. --Kafka Consumer can now auto-commit when stopped. The values for the ʻautoCommitOnStop option are: sync, ʻasync, none`
--Box component
--Migrated to v2 Java API.
--JPA component
--Added query support for JPA Producer.
Recommended Posts