anchor.diff:  Camel contexts. That may be useful, for example, for Camel routes that
   may be required to be added later during the application execution.
   
  +NOTE: Since Camel version 2.17.0, Camel CDI is capable of managing any kind of
  +`CamelContext` beans (e.g. `DefaultCamelContext`). In previous versions, it is only capable of managing beans
  +of type `CdiCamelContext` so it is required to extend it.
  +
   The CDI qualifiers declared on the `CamelContext` beans are also used to
   bind the corresponding Camel primitives, e.g.:
   
  
positive.code: The following examples are available in the `examples` directory of the
  Camel project:
  
  * `camel-example-cdi-metrics` - illustrates the integration between
  Camel, Dropwizard Metrics and CDI,
  * `camel-example-cdi-properties` - illustrates the integration between
  
negative.code: See Also
  ^^^^^^^^
  
  * http://www.cdi-spec.org[CDI specification Web site]
  * http://www.cdi-spec.org/ecosystem/[CDI ecosystem]
  * http://weld.cdi-spec.org[Weld home page]
  * http://openwebbeans.apache.org[OpenWebBeans home page]
  * https://github.com/astefanutti/further-cdi[Going further with CDI and Camel]
  (See Camel CDI section)
  