{"id":60868,"date":"2016-10-14T07:00:04","date_gmt":"2016-10-14T04:00:04","guid":{"rendered":"https:\/\/www.javacodegeeks.com\/?p=60868"},"modified":"2016-10-13T16:21:33","modified_gmt":"2016-10-13T13:21:33","slug":"apache-camel-2-18-released-whats-included","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2016\/10\/apache-camel-2-18-released-whats-included.html","title":{"rendered":"Apache Camel 2.18 Released – Whats included"},"content":{"rendered":"

This week\u00a0Apache Camel 2.18.0<\/a> was released. This release is a significant release which I will highlight in this blog post.
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n\"2018\"<\/a><\/p>\n

Java 8<\/b><\/p>\n

Camel 2.18 is the first release that requires Java 1.8 (eg easy to remember Camel 2.18 = Java 1.8. Camel 2.17 = Java 1.7). We have taken a cautious approach and kept the Camel API backwards compatible in the sense as an end user you can take your existing Camel application source code and re-compile them with Java 1.8 and Camel 2.18 and you should be all good.<\/p>\n

Internally in the Camel source code we have started using Java 8 APIs for new functionality. Existing functionality is still using Java 7 APIs so we can easily backport bug fixes to the older versions.<\/p>\n

We have also gently introduced a few Java 8 lambda\/functional APIs into the Java RouteBuilder you can use in predicates and message transformations. You can view a little example at\u00a0github<\/a>.<\/p>\n

Spring Boot Starters<\/b><\/p>\n

We had support for Spring Boot since Camel 2.15, but in this release we have curated all the Camel components to align and make them work as first class\u00a0Spring Boot starter components<\/a>. This means you should use -starter as your dependencies, such as camel-kafka-starter.<\/p>\n

Spring Boot Auto Configuration<\/b><\/p>\n

All the Camel components now generate Spring Boot auto configuration source code which means you can configure components, data formats, languages etc using Spring Boot configuration. For example in the application.properties file. And on top of that tooling such as IDEA, Eclipse etc which has support for Spring Boot will have code completions when editing the application.properties file.<\/p>\n

\"sb-auto\"<\/a><\/p>\n

Nicola Ferraro whom help implement posted a\u00a0blog entry<\/a> with more details.<\/p>\n

Spring Boot Health Check<\/b><\/p>\n

Apache Camel comes with health check integrated with Spring Boot if you are using actuators. The health check does a coarse grain check that Camel did start up properly. We plan to implement a deeper Health Check API in Camel to allow individual components to participate in the check. For example to check if the component can connect to a remote system and so on.

<\/div> <\/div><\/p>\n

WildFly-Swarm Camel<\/b><\/p>\n

The\u00a0WildFly Swarm<\/a> project also has great support for Apache Camel. However this development happens at the wildfly-camel project.\u00a0WildFly-Camel<\/a> released version 4.3.0 that supports Camel 2.18.0.<\/p>\n

Automatic Documentation<\/b><\/p>\n

I have previously blogged about that we are working on keeping and generating the Camel documentation from the source code. This means that every Camel component, eip, language, data format etc. all have their options documented in the source code, which we then extract during build and keep the accompanying documentation up to date. We have migrated almost all the documentation from the old wiki system to .adoc files in the source code. We will continue this work to complete this for the next release, and will work on build a new website.<\/p>\n

As a Camel developer you may think its not a big deal but really it is. This ensures that all options are always 100% up to date in the documentation. It also allows tooling to access this information at both design and runtime. hawtio can at runtime display deep level information about all your endpoints and include the documentation for each option as shown:<\/p>\n

\"camel-hawtio-doc\"<\/a><\/p>\n

We also have a \u00a0Maven plugin<\/a>\u00a0that can scan all your source code and report invalid configuring Camel endpoints. This plugin is currently hosted at\u00a0fabric8<\/a> where we can foster innovation faster. However when the plugin matures then we plan to donate the source code to Apache Camel project to be included out of the box.<\/p>\n

XML XSD fully documented<\/b><\/p>\n

The XML XSD for Spring and Blueprint now also includes documentation for the configuration you can do outside routes, such as on\u00a0and other global configurations.<\/p>\n

FluentProducerTemplate<\/b><\/p>\n

One of the smaller but really lovely new additions is the FluentProducerTemplate which is using a fluent style API as a client API for sending a message to a Camel endpoint. Now you can do this nicely with<\/p>\n

template().withBody(\"Hello World).withHeader(\"foo\", 123\").withHeader(\"bar\", 456).to(\"jms:queue:beer\").send();<\/pre>\n
Rest Producer<\/b><\/p>\n
The Rest component allows to call REST services now (as a client), where you can pick one of the following Camel components for the HTTP transport: http, http4, netty4-http, jetty, restlet, undertow. You can also refer to a existing swagger api doc and include camel-swagger-java on the classpath, for automatic validation of rest endpoint is configured to use a valid rest operation\/parameters.<\/p>\n
Circuit Break using Hystrix<\/b><\/p>\n
We added native support for using Netflixx\u00a0Hystrix<\/a> as circuit break in your Camel routes. There is an\u00a0example included<\/a>.<\/p>\n
Below is\u00a0another example<\/a> from an example with Spring Boot calling a service running on WildFly Swarm that runs on Kubernetes cluster (or local) which I have been giving talks about recently.<\/p>\n
public void configure() throws Exception {\r\n\r\nfrom(\"timer:foo?period=2000\")\r\n\r\n.hystrix()\r\n\r\n.to(\"netty4-http:http:\/\/{{service:helloswarm}}\/say\")\r\n\r\n.onFallback()\r\n\r\n.setBody().constant(\"Nobody want to talk to me\")\r\n\r\n.end()\r\n\r\n.log(\"${body}\");\r\n\r\n}<\/pre>\n
Zipkin message tracing<\/b><\/p>\n
The release also includes camel-zipkin which allows to use zipkin for distributed message tracing. You can find more details with the\u00a0provided example<\/a>.<\/p>\n
ServiceCall<\/b><\/p>\n
The\u00a0Service Call EIP<\/a> allows to call remote services with service discovery from a pluggable service registry. For example you can use etdc, consul, ribbon, kubernetes and others are coming.<\/p>\n
New Components<\/b><\/p>\n
As usual each release comes with a number of new components:<\/p>\n