anchor.diff:  
   === Camel Karaf
   
  -The following features has been removed due they become not compatible with OSGi: `camel-atmosphere-websocket`.
  +The following feature has been removed due to being no longer compatible with OSGi: `camel-atmosphere-websocket`.
   
   === CamelFileDataSource
   
  -Class `CamelFileDataSource` has moved from `camel-http-common` in package `org.apache.camel.http.common` to `camel-attachments` package `org.apache.camel.attachment.CamelFileDataSource`.
  +The class `CamelFileDataSource` has moved from `camel-http-common` package `org.apache.camel.http.common` to `camel-attachments` package `org.apache.camel.attachment`.
   
   If your code directly depends on this class, you will need to update the package reference to the new location.
   
  
positive.code: === Stream Caching
  
  If stream caching is enabled and an exception is thrown while converting the message payload to `StreamCache` then the error handler
  can now handle this exception (eg onException). The exception is regard as non-recoverable and redelivery is not in use.
  
  === Camel Caffeine
  
  To configure the component to use a pre-configured cache, it is not more required to use the now removed `cache` option as the component perorm a look-up from the registry based on the `cacheName` URI param.
  
  As example, the following code:
  
  
negative.code: }
  ----
  
  As the customizers are now taken into account as part of the standard lifecycle of the `CamelContext`, to programmatically configure a component, it is enough to register the appropriate customizer in the `Registry`. For example:
  
  [source,java]
  ----
  