anchor.diff:  the method option (see below for more details).
   * you can explicitly specify the method name in the xref:dsl.adoc[DSL]
   or when using xref:pojo-consuming.adoc[POJO Consuming] or
  -xref:pojo-producing.adoc[POJO Producing]
  -* if the bean has a method marked with the `@Handler` annotation, then
  -that method is selected
  +xref:pojo-producing.adoc[POJO Producing].
  +* if the bean has a method annotated with the `@Handler` annotation, then
  +that method is selected.
   * if the bean can be converted to a xref:processor.adoc[Processor] using
   the xref:type-converter.adoc[Type Converter] mechanism, then this is
   used to process the message. The xref:components::activemq-component.adoc[ActiveMQ] component
  
positive.code: * if the bean class is private (or package-private), interface methods
  will be preferred since Camel can't invoke class methods on such beans
  
  In cases where Camel cannot choose a method to invoke, an
  `AmbiguousMethodCallException` is thrown.
  
  By default, the return value is set on the outbound message body.
  
  == Asynchronous processing
  
  You can return a `CompletionStage` implementation (e.g. a `CompletableFuture`)
  to implement asynchronous processing.
  
  Please be sure to properly complete the CompletionStage with the result
  
negative.code: can occur in different ways, in the following order of importance:
  
  * if the message contains the header *CamelBeanMethodName* then that
  method is invoked, converting the message to the type of the method's
  parameter.
  ** You can qualify parameter types to select
  exactly which method to use among overloads with the same name (see
  below for more details).
  