anchor.diff:  ====
   
   
  +
   [[beans-autowired-annotation-primary]]
   === Fine-tuning annotation-based autowiring with @Primary
   
  
positive.code: 	</beans>
  ----
  
  .Full @Configuration vs 'lite' @Beans mode?
  ****
  When `@Bean` methods are declared within classes that are __not__ annotated with
  `@Configuration` they are referred to as being processed in a 'lite' mode. For example,
  bean methods declared in a `@Component` or even in a __plain old class__ will be
  considered 'lite'.
  
  Unlike full `@Configuration`, lite `@Bean` methods cannot easily declare inter-bean
  dependencies. Usually one `@Bean` method should not invoke another `@Bean` method when
  operating in 'lite' mode.
  
  Only using `@Bean` methods within `@Configuration` classes is a recommended approach of
  ensuring that 'full' mode is always used. This will prevent the same `@Bean` method from
  accidentally being invoked multiple times and helps to reduce subtle bugs that can be
  hard to track down when operating in 'lite' mode.
  ****
  
  The `@Bean` and `@Configuration` annotations will be discussed in depth in the sections
  below. First, however, we'll cover the various ways of creating a spring container using
  Java-based configuration.
  
  [[beans-java-instantiating-container]]
  === Instantiating the Spring container using AnnotationConfigApplicationContext
  
negative.code: 	@Autowired
  	private List<Store<Integer>> s;
  ----
  
  
  
  