anchor.diff:  ----
   
   link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#producer_method[Producer]
  -and link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#disposer_method[disposer] methods
  -can also be used as well to customize the Camel context bean, e.g.:
  +and link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#disposer_method[disposer]
  +methods can also be used as well to customize the Camel context bean, e.g.:
   
   [source,java]
   ----
  
positive.code: endpoint instances and the observer methods as the CDI container doesn't
  have any ways of discovering the Camel context model during the
  deployment phase.
  
  [[CDI-Auto-configuredOSGiintegration]]
  Auto-configured OSGi integration
  
negative.code: 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.:
  