anchor.diff:  interface that can be customized on a
   http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html[CamelContext].
   
  -The default implementation,
  -http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html[DefaultTypeConverter],
  -uses pluggable strategies to load type converters via
  -http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/TypeConverterLoader.html[TypeConverterLoader].
  -The default strategy,
  -http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/AnnotationTypeConverterLoader.html[AnnotationTypeConverterLoader],
  -uses a discovery mechanism to find converters.
  -
  -*New in Camel 1.5*
  -
  -The default implementation,
  -http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html[DefaultTypeConverter],
  -now throws a
  -http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/NoTypeConversionAvailableException.html[NoTypeConversionAvailableException]
  -if a suitable conversion cannot be found
  -(https://issues.apache.org/jira/browse/CAMEL-84[CAMEL-84]).
  -The semantical ambiguity of `null` (both valid result and indication
  -of no conversion found) is now resolved, but this may impact existing
  -code in that it should now catch the exception instead of checking
  -for `null`.
  +Camel provides two type converter registy implementations:
  +
  +- FastTypeConverterRegistry (new default)
  +- DefaultTypeConverterRegistry (old)
  +
  +From Camel 3 onwards there is a faster type converter registry implementation that is enabled by default. This implementation uses source code generation via the `camel-apt` compiler plugin to generate source code, that allows Camel at runtime to load and invoke these type converters via quick java method invocations. The older implementation in Camel 2 uses a annotation based discover to load and register type converters and invokes the type converters via Java method call reflections.
  +
   
   [[TypeConverter-TypeConverterRegistry]]
   ==== TypeConverterRegistry
  -
  -*New in Camel 2.0*
   
   Exposed the
   http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/TypeConverterRegistry.html[TypeConverterRegistry]
  
positive.code: }
  ----
  
  Static methods are invoked; non-static methods require an instance of
  the converter object to be created (which is then cached). If a
  converter requires configuration you can plug in an Injector interface
  to the `DefaultTypeConverter` which can construct and inject converter
  objects via Spring or Guice.
  
  We have most of the common converters for common Java types in the
  http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/converter/package-summary.html[org.apache.camel.converter]
  package and its children.
  
  [[TypeConverter-Returningnullvalues]]
  ===== Returning null values
  
negative.code: [[TypeConverter-WritingyourownTypeConverters]]
  ==== Writing your own Type Converters
  
  You are welcome to write your own converters. Remember to use the
  `@Converter` annotations on the classes and methods you wish to use.
  And on the top-level class add `Converter(loader = true)` to support the _fast way_
  of using type converters.
  
  * static methods are encouraged to reduce caching, but instance methods
  are fine, particularly if you want to allow optional dependency
  injection to customize the converter
  * converter methods should be thread safe and reentrant
  
  [[TypeConverter-Exchangeparameter]]
  ==== Exchange parameter
  
  The type converter accepts the `Exchange` as an optional 2nd parameter.
  This is usable if the type converter for instance needs information from
  