Page History

...

• 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.
• Upgraded camel-hbase to Hadoop 2.x and HBase 1.1.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
• 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 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
    

...