anchor.diff:  for dealing object to object mapping headaches that crop up in
   enterprise integration projects.
   
  -To explain how Dozer can be uses within Camel we'll use the following
  +To explain how Dozer can be used within Camel we'll use the following
   example of a simple Customer Support Service. The initial version of the
   Service defined a 'Customer' object used with a very flat structure.
   
  
positive.code: 
  [source,java]
  -----------------------------------------------------------------------------------------
  DozerBeanMapper mapper = new DozerBeanMapper(Arrays.asList(new String[]{"mapping.xml"}));
  new DozerTypeConverterLoader(camelContext, mapper);
  -----------------------------------------------------------------------------------------
  
  Or in Spring
  
  [source,xml]
  ----------------------------------------------------------------------------------------------------
  <!-- the registry will be scanned and 'mapper' below will be found and installed -->
  <bean id="dozerConverterLoader" class="org.apache.camel.converter.dozer.DozerTypeConverterLoader" />
  
  <bean id="mapper" class="org.dozer.DozerBeanMapper">
    <property name="mappingFiles">
      <list>
        <value>mapping.xml</value>
      </list>
    </property>
  </bean>
  ----------------------------------------------------------------------------------------------------
  
  [[DozerTypeConversion-ConfiguringinOSGiblueprint]]
  Configuring in OSGi blueprint
  -----------------------------
  
  *Available as of Camel 2.12*
  
  When using Dozer with OSGi Blueprint then its works better by
  configuring Dozer using the
  `org.apache.camel.converter.dozer.DozerBeanMapperConfiguration` instead
  of `org.dozer.DozerBeanMapper`, as shown below:
  
  [source,xml]
  --------------------------------------------------------------------------------------------------
  <bean id="dozerConverterLoader" class="org.apache.camel.converter.dozer.DozerTypeConverterLoader">
    <argument index="0" ref="myCamel"/>
    <argument index="1" ref="mapper"/>
  </bean>
  
  <bean id="mapper" class="org.apache.camel.converter.dozer.DozerBeanMapperConfiguration">
    <property name="mappingFiles">
      <list>
        <value>mapping.xml</value>
  
negative.code: `DozerTypeConverterLoader` providing it the camel context and an
  optional Dozer mapper. If no mapper is supplied, Camel's registry will
  be searched for suitable instances. The loader will query the Dozer
  Mapper for the types it converts and register them with Camel's
  type conversion framework to be handled by the mapper.
  
  [NOTE]
  