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: 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 body to the type of the method's
  argument.
  ** You can qualify parameter types to select
  exactly which method to use among overloads with the same name (see
  below for more details).
  
negative.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 invoked.
  
  NOTE: This requires to include `camel-bean` as dependency on the classpath.
  
  