Camel 2.17.0

...

Release

...

Welcome to the 2.17.0 release (currently in progress) which resolved approx XXX . 450 issues (new features, improvements and bug fixes such as)...)

• The component documentation generated from the source code has been double checked to be up to date and include all the options the endpoints supports.
• Reworked the Apache Karaf feature to not install camel-spring by default. The problem is camel-spring is using spring-dm which is only supports Spring 3.x, and therefore Spring 3.x was installed and used. All the Camel features that uses Spring JARs are now using Spring 4.x.
• Camel commands for Spring Boot
• Many improvements to Camel Kura
• Added transacted option to SQL Component when used as a consumer in a transacted route.
• Added support for UPDATE operation to ElasticSearch.
• Allow to reuse existing configured Elasticsearch Client on the ElasticSearch component, instead of creating a client per endpoint. 
• The include and exclude options on File2 and FTP endpoints is now case in-sensitive out of the box.
• Resource based component such as XSLT, Velocity etc can load the resource file from the Registry by using ref: as prefix.
• Upgraded camel-amqp to the latest qpid-jms-client (also AMQP < 1.0 is not supported anymore).
• Many improvements to Camel AMQP component.
• The Metrics Component allows to capture Message History performance statistics with the MetricsMessageHistoryFactory 
• Reduced the number of mbeans enlisted in the services tree, to only include mbeans that has value to be managed.
• The Elasticsearch Component now supports MultiGet operation
• The Throttler has been improved to be more performant and use a rolling window for time periods which gives a better flow.
• The setHeader and setExchangeProperty allows to use a dynamic header key using the Simple language if the name of the key is a Simple language expression.
• Add collate function to Simple language to make it easier to split a message body into sub lists of a specified size. The function is similar to the collate function from Groovy.
• The Camel Run Maven Goal is able to auto detect if its a OSGi Blueprint or CDI project so end users no longer have to explicit configure this on the plugin.
• Camel-Elasticsearch now supports Multiget, Multisearch and exists operation
• Camel-Git now supports Cherry-pick operation
• Stopping the Main class from JMX will now trigger shutdown of the Main class/JVM also, as it does when hitting ctrl + c.
• Added option to skipFirst to the Tokenizer language to make it easy to skip the very first element, when for example splitting a CSV file using the Splitter EIP.
• The Rest DSL now supports default values for query parameters
• The Rest DSL now only binds from POJO to JSon/XML if the content-type is for json or xml. This allows you to specify a custom content-type and omit the binding, such as when having binary payloads.
• Exchange and Message only output id in their toString method to avoid outputting any message details such as sensitive details from message bodies.
• Camel Error Handler no longer log message body/header details when logging the Message History. This avoids logging any sensitive details from message bodies.
• Camel Exception Clause and Error Handler now supports using a custom Processor to be invoked right after an exception was thrown using the new onExceptionOccurred option.
• RabbitMQ consumer more resilient to auto re-connect in case of connection failures
• The JSON camel-jackson can be used as a type converter to convert json to/from POJO and String/byte[] types, if enabled.
• The SQL Component now supports loading the SQL queries from external files on the classpath or file system, where you can format the queries using newlines and indenting.
• The Mail consumer allows to use an idempotent repository which allows to cluster consuming from the same mailbox, and let the repository coordinate whether a mail message is valid for the consumer to process.
• Added support for completion interval on the SJMS Batch component, which allows to trigger batch completion in a fixed scheduled interval.
• The HTTP and HTTP4 producers now support the disableStreamCache option to allow to use the raw response stream as the message body instead of wrapping using Stream caching
• The Camel CDI component has been improved to better fit into the CDI programming model, cover a larger set of containers, and provide these new features:
  • The Camel events from the org.apache.camel.management.event package (like CamelContextStartedEvent) can be observed as CDI events
  • The new CDI event Camel endpoint enable CDI events to be seamlessly consumed from (respectively produced by) Camel consumers (respectively Camel producers)
  • CDI beans annotated with the @Converter annotation are automatically registered as type converters
  • The CDI Camel contexts can be properly customised programmatically in bean constructor or @PostConstruct lifecycle callback
  • Camel routes configured in RouteBuilder beans are added before the corresponding Camel contexts get started
  • CDI Camel contexts are now properly adapted when deployed in OSGi containers and are registered as OSGi services
  • Proper support of multiple Camel contexts across all the features
    
  • A new Camel CDI Test module is available to ease testing of Camel CDI applications
• The XSLT component now supports Saxon's integrated extension functions.
• Added option reuseChannel to Netty4 which allows to reuse existing Channel when using a netty producer to call a server multiple times during routing an Exchange.
• Idempotent Repository now supports optional serialized headers 
• Rest DSL adjusted to swagger spec 2.0 and Swagger Java as well.
• Rest DSL allows to specify response headers as well.
• Rest DSL is exposing the REST services using all local IP address (eg 0.0.0.0) by default.
• Camel-quartz2 now supports customCalendar to avoid specific range of dates (Holidays for example) in Scheduler and Triggers.
• Improved Bean Language to be able to invoke static methods on pure static classes.
• When Bean Language failed to invoke a method from an OGNL method chain (eg invoke the following 3 methods "doFoo.doSomething.getBar") and a method returned null which prevent further method invocation as that would cause a NullPointerException. Now you have a more detailed exception message to better explain this.
• JAXB data format and type converter now supports converting from XML to POJO for classes that are using ObjectFactory classes instead of XmlRootElement annotations.
• The Kafka component has been migrated to use the Java Kafka client instead of Scala. As such there may be migration efforts or code changes that can affect users upgrading.
• The Loop EIP now allows to run in a while loop mode, so it loops until the predicate returns false.
• Improved Rest DSL when CORS enabled to process and return the configured CORS headers in the rest-dsl in all the supported Rest DSL components.
• The options verb in the Rest DSL has been deprecated and are not in use if CORS is enabled.
• The LogEIP allows to use a global configured log name, instead of using route id as the logger name
• A new camel-spring-boot-starter module that is a Spring-Boot starter module like any other starter modules.
• Allow to run Camel Spring Boot applications and keep the JVM running in a easy way by setting camel.springboot.main-run-controller = true option.
• The SQL Component supports using SQL IN queries in the producer where the number of values in the IN clause is dynamic from the current exchange.
• The Swagger Java module now supports YAML as response format in addition to the exisitng JSon format.

...

...

Getting the Binaries using Maven 2

...

<dependency>
  <groupId>org.apache.camel</groupId>
  <artifactId>camel-core</artifactId>
  <version>x<version>2.y17.x<0</version>
</dependency>

SVN Tag Checkout

svn co http://svn.apache.org/repos/asf/camel/tags/camel-x2.y17.x0

Changelog

For a more detailed view of new features and bug fixes, see the:

• release Release notes for x2.y17.x0