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: }
  
  // service objects can be sent to the processor and automagically converted by Camel & Dozer
  template.sendBody("direct:legacy-service-in",new org.apache.camel.converter.dozer.service.Customer("Bob", "Roberts", "12345", "1 Main st."));
  ---------------------------------------------------------------------------------------------------------------------------------------------
  
negative.code: </camelContext>
  --------------------------------------------------------------------------------------------------
  
  You should of noticed that the configuration for Spring or OSGi Blueprints
  is the same, except for the 'xmlns' for the 'camelContext'.
  
  Now, where necessary, Camel will use Dozer to do conversions; in our
  case between the new domain and legacy Customer types e.g.
  
  [source,java]
  