Page History

...

Welcome to the 2.19.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

• The Camel Maven Plugin now provides the camel:validate goal to parse your Java and XML source code for any Camel routes and report invalid Camel endpoint uri and simple expression errors. You can run this at code time (not runtime). 
• Returning null from Bean should work similar to how setBody and transform works when they set a null body.
• The Camel Spring Boot starter components now have their auto configuration depends on org.apache.camel.springboot.CamelAutoConfiguration which makes it easier writing unit tests where you can exclude org.apache.camel.springboot.CamelAutoConfiguration to turn off Camel Spring Boot auto configuration completely.
• Camel now supports OWASP dependency check maven plugin
• Camel-Nats component now supports TLS
• Camel-Nats component now supports explicit flushing (with timeout) of the connection
• Camel-Metrics component now supports Gauge type
• File consumer now supports idempotent-changed and idempotent-rename read lock strategies for clustering. 
• Camel Catalog now supports custom runtime providers that only includes the supported Camel components, languages and data formats running in that container. For example for Karaf or Spring Boot in the camel-catalog-provider-karaf and camel-catalog-provider-springboot.
• The bean component will when calling a method that returned an instance of Callable now call that callable to obtain the chained result. This allows to call Groovy functions/closures etc.
• Failover Load Balancer with inheritErrorHandler=false, now allows Camel's Error Handler to react after the load balancer is exhausted.
• Salesforce component now supports limits, recent items and approvals
• Dumping Camel routes as XML now includes custom namespaces which are at xpath expressions etc. Likewise updating Camel routes from XML can now include namespaces which will be associated on xpath expressions.
• Added RouteIdFactory which can auto assign route ids based on the consumer endpoints to use more sensitible names, instead of route1, route2, etc.

...