anchor.diff:  How bean methods to be invoked are chosen (if they are not specified
   explicitly through the *method* parameter) and how parameter values are
   constructed from the Message are all defined by the
  -Bean Binding mechanism which is used throughout
  -all of the various Bean Integration
  -mechanisms in Camel.
  +xref:manual::bean-binding.adoc[Bean Binding] mechanism which is used throughout
  +all the various xref:manual::bean-integration.adoc[Bean Integration] mechanisms in Camel.
  +
  +See also related xref:bean-language.adoc[Bean Language].
  +
   
   
   
  
positive.code: -------------------------------------------------------
  
  Instead of passing name of the reference to the bean (so that Camel will
  lookup for it in the registry), you can specify the bean itself:
  
  [source,java]
  ---------------------------------------------------------------
  
negative.code: include::partial$component-endpoint-headers.adoc[]
  // component headers: END
  
  == Examples
  
  A *bean:* endpoint cannot be defined as the input to the route; i.e. you
  cannot consume from it, you can only route from some inbound message
  Endpoint to the bean endpoint as output, such as the *direct* endpoint as input.
  
  Suppose you have the following POJO class to be used by Camel
  
  [source,java]
  ----
  package com.foo;
  
  public class MyBean {
  
      public String saySomething(String input) {
          return "Hello " + input;
      }
  }
  ----
  
  Then the bean can be called in a Camel route by the fully qualified classname:
  
  [source,java]
  ----
  from("direct:hello")
     .to("bean:com.foo.MyBean");
  ----
  
  And in XML DSL:
  
  [source,xml]
  ----------------------------
  <route>
     <from uri="direct:hello"/>
     <to uri="bean:com.foo.MyBean"/>
  </route>
  ----------------------------
  
  What happens is that when the exchange is routed to the MyBean, then Camel
  will use the Bean Binding to invoke the bean, in this case the _saySomethinh_ method,
  by converting the `Exchange` in body to the `String`
  type and storing the output of the method back to the Exchange again.
  
  TIP: The bean component can also call a bean by _bean id_ by looking up the bean
  in the xref:manual::registry.adoc[Registry] instead of using the class name.
  
  == Java DSL specific bean syntax
  
  Java DSL comes with syntactic sugar for the xref:bean-component.adoc[Bean]
  component. Instead of specifying the bean explicitly as the endpoint
  