6.5. Component Updates

Since Apache Camel version 2.13.0, upgraded from 7.6.x to 8.1.x.

Since Apache Camel version 2.13.0, the Hazelcast component uses Object instead of String as the key type.

Since Apache Camel version 2.13.0, the atomic number producer uses a different atomic number name. This is due to the bug fix, CAMEL-6833 (previously, the wrong atomic number name was used).

Since Apache Camel version 2.13.0, the instance consumer writes headers to the in message (previously, the instance consumer was incorrectly writing headers to the out message instead of the in message).

Since Apache Camel version 2.13.0, the erroneous header value, envict, sent by the map/multimap consumer has now been corrected to evicted.

Since Apache Camel version 2.13.0, the NON_BLOCKING enum value has been removed from the APNS component, because it is no longer support in APNS itself.

Since Apache Camel version 2.13.0, the Language component no longer caches the compiled script, because that could cause unwanted side-effects. You can set cacheScript=true to enable the previous behaviour, if you are sure that your script does not cause such side-effects.

Since Apache Camel version 2.13.0, the default value of the urlDecodeHeaders option on the Netty HTTP component has been changed from true to false.

Since Apache Camel version 2.14, Netty HTTP now removes the headerFilterStrategy option after resolving it.

Since Apache Camel version 2.13.0, the Cache component no longer includes the ehcache.xml configuration file. The default EHCache configuration is used instead, if you do not specify a configuration file explicitly.

Since Apache Camel version 2.13.0, the CDI component has been upgraded from DeltaSpike 0.3 to 0.5, which may affect upgrades.

Since Apache Camel version 2.13.0, when creating a consumer, the default value of NoLocal has changed from true to false.

Since Apache Camel version 2.13.0, added beforeAddRoutes and afterAddRoutes methods to org.apache.camel.component.servletlistener.CamelContextLifecycle class.

Since Apache Camel version 2.14, the useSsl option has been removed, because SSL/TLS is now always enabled (this is enforced by Twitter).

Since Apache Camel version 2.14, the Restlet component has been fixed to return error code 405 (instead of 404), if a HTTP method is not allowed.

Since Apache Camel version 2.14, routes starting with a JMS endpoint will now shut down the consumer (implemented by MessageListenerContainer) quicker when CamelContext is being stopped. This can help to achieve a cleaner shutdown, as otherwise some JMS clients might attempt to re-connect or fail over during the shutdown . If you want to disable this behaviour, so that the routes keep accepting messages during Camel shutdown, set acceptMessagesWhileStopping=true.

Since Apache Camel version 2.14, this component caches the bean by default (that is, a single instance of the bean is used and re-used). This behaviour can be turned off by setting cache=false, which implies that a new instance of the bean is created for every method invocation (that is, there is no re-use).

Since Apache Camel version 2.15, the transformerFactory option now uses the with the #BeanID syntax to reference a bean instance.

Since Apache Camel version 2.15, Java endpoint API has been refactored somewhat.

Since Apache Camel version 2.15, upgraded to Apache Commons CSV version 1.x, which has a different API to the 0.x version.

Since Apache Camel version 2.15, the API has been refactored.

Since Apache Camel version 2.15, the need for runtime-specific servlets in Swagger has been eliminated. You can just use the default servlet, which is provided out of the box.

Since Apache Camel version 2.15, no longer sends headers whose key starts with Camel, as those are consider internal headers and should not be included in the sent emails.

Since Apache Camel version 2.15, the delay option has changed from using seconds to milliseconds as the time unit.

Since Apache Camel version 2.15, you cannot use the Bean component as a consumer endpoint (from, at the start of a route). To get the same effect, you can start the route with a scheduler endpoint and send to a bean instance (using to("bean:BeanID") or beanRef("BeanID")).