anchor.diff:  * 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
  +In cases when Camel cannot choose a method to invoke, an
   `AmbiguousMethodCallException` is thrown.
   
  -By default, the return value is set on the outbound message body.
  +By default, the return value is set in the outbound message body.
   
   == Asynchronous processing
   
  -You can return a `CompletionStage` implementation (e.g. a `CompletableFuture`)
  +You can return a `CompletionStage` implementation (e.g. `CompletableFuture`)
   to implement asynchronous processing.
   
   Please be sure to properly complete the CompletionStage with the result
  
positive.code: 
  Bean Binding in Camel defines both which methods are invoked and also
  how the xref:components:eips:message.adoc[Message] is converted into the parameters of
  the method when it is invoked.
  
  NOTE: This requires to include `camel-bean` as dependency on the classpath.
  
  
negative.code: 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 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
  