context:component-scan 엘리먼트는 annotation-config도 등록해줌.

이클립스에서 F2를 이용해서 읽어봤습니다.

Scans the classpath for annotated components that will be auto-registered as
 Spring beans. By default, the Spring-provided @Component, @Repository,
 @Service, and @Controller stereotypes will be detected. Note: This tag implies the
 effects of the ‘annotation-config’ tag, activating @Required, @Autowired,
 @PostConstruct, @PreDestroy, @Resource, @PersistenceContext and
 @PersistenceUnit annotations in the component classes, which is usually desired
 for autodetected components (without external configuration). Turn off the
 ‘annotation-config’ attribute to deactivate this default behavior, for example in order
 to use custom BeanPostProcessor definitions for handling those annotations. Note:
 You may use placeholders in package paths, but only resolved against system
 properties (analogous to resource paths). A component scan results in new bean
 definition being registered; Spring’s PropertyPlaceholderConfigurer will apply to
 those bean definitions just like to regular bean definitions, but it won’t apply to the
 component scan settings themselves.

Content Model : (include-filter*, exclude-filter*)

수확이 있었군, 스프링 공부할 때 살펴볼 클래스가 하나 등장했다. PropertyPlaceholderConfigurer
설정 파일 읽어서 BeanDefinition 객체로 만든다는것 까진 알고 있었는데, 어디서 누가 하는진 몰랐는데 저 녀석이 하고 있었나 봅니다. 캬오~ JavaDoc 귿이야..