Page History

...

• This is the last release that will support Java 1.7. Releases after this is expected to require Java 1.8+. 
• Any custom component that supports suspension in doSuspend/doResume should implement the new Suspendable marker interface, so Camel knows there is custom logic for suspension in the component.
• Exchange and Message only output id in their toString method to avoid outputting any message details such as sensitive details from message bodies.
• Removed camel-hbase as Karaf feature as it did not really work well in OSGi
• camel-infinispan requires Java 8.
• Support for Spring 4.0.x is deprecated. Support for Spring 3.x is being removed in the next release.
• Moved some Camel tooling related dependencies (such as maven/plexus) from the Camel Parent BOM to the tooling BOM (to have them separated).
• camel-amqp do not support 0.9 anymore. 
• camel-spring-integration feature has been removed from the Camel karaf.
• The Mail component now requires to configure to, cc, and bcc using lower case keys, eg to=foo@bar.com, instead of To=foo@bar.com as previously.
• The File consumer no longer probe the file content by default. See the option probeContentType for more details.
• If using Bean or Class component and specifying additional parameters in the endpoint uri to configure on the bean, then these options should now be prefixed with bean., eg foo=123 is now bean.foo=123.
• The Twitter delay option is changed from seconds to milli seconds by default, eg 10 should be 10000 to indicate 10 seconds. This is aligned how other components with delay option behaves. 
• The options attributeNames and messageAttributeNames on AWS-SQS is changed to a string type where you can separate multiple values using comma. Before the type was a Collection which was much harder to configure in the Camel uris.
• The hbase component now require row mapping from the endpoint uri to be prefixed with row. as prefix.
  Before: family=info&qualifier=firstName&family2=birthdate&qualifier2=year. After: row.family=info&row.qualifier=firstName&row.family2=birthdate&row.qualifier2=year.
• As part of the Camel CDI component refactoring, DeltaSpike is not used anymore for the sourcing of the configuration properties. This new version of the component is agnostic to any configuration sourcing mechanism and delegates that concern to the application so that it can declare a custom PropertiesComponent bean whose sourcing is tailored to its need. DeltaSpike can still be used by the application by declaring a PropertiesComponent bean configured with a PropertiesParser relying on DeltaSpike. See the camel-example-cdi-properties example for more details.

...