anchor.diff:          // do something on bean
           return bean;
       }
  +
  +    public void configure(CamelContext camelContext) throws Exception {
  +        // this method is optional and can be omitted
  +        // do any kind of configuration here if needed
  +    }
  +
   }
   ----
   
  
positive.code: When running Camel standalone via `camel-main` JAR, then Camel will use package scanning to discover:
  
  - Camel routes by discovering `RouteBuilder` classes
  - Camel configuration classes by discovering `CamelConfiguration` classes
  - Camel type converters by discovering classes annotated with `@Converter`
  
  To use package scanning then Camel needs to know the base package to use as _offset_. This
  
negative.code: 
  This is similar to Spring Boot where you can also do this with the Spring Boot `@Bean` annotations,
  or in Quarkus/CDI with the `@Produces` annotation.
  
  === Using annotation based configuration classes
  
  Instead of configuration classes that implements `CamelConfiguration`, you can annotate the class with `org.apache.camel.@Configuration` as shown:
  
  [source,java]
  ----
  @Configuration
  public class MyConfiguration {
  
      @BindToRegistry
      public MyBean myAwesomeBean() {
          MyBean bean = new MyBean();
          // do something on bean
          return bean;
      }
  }
  ----
  
  == Specifying custom beans
  
  