Add @ComponentScan annotation [SPR-7194]

[spring-projects-issues]

Eric Sirianni opened SPR-7194 and commented

It would be useful to have the @ComponentScan from JavaConfig in Spring core to enable programmatic component scanning. The workaround of using AnnotationConfigWebApplicationContext and setting "init-param" of "contextConfigLocation" is OK, but not a great long-term solution.

The referenced thread talks about porting some of the features of JavaConfig that didn't make it into Spring 3.0.

So hopefully the use-case is well appreciated - I'm just filing this bug for tracking purposes.

---

Affects: 3.0.2

Reference URL: http://forum.springsource.org/showthread.php?t=80761

Issue Links:

• Support Java-Based Application Configuration [SPR-7420] #12078 Support Java-Based Application Configuration
• Allow recursive use of @ComponentScan [SPR-8307] #12956 Allow recursive use of @ComponentScan
• Introduce ComponentScanSpec for ComponentScanBeanDefinitionParser (context:component-scan) [SPR-8143] #12794 Introduce ComponentScanSpec for ComponentScanBeanDefinitionParser (context:component-scan) ("supersedes")

13 votes, 9 watchers

[spring-projects-issues]

Baruch Sadogursky commented

There are other features of JavaConfig project missing as well - @AspectJAutoProxy, @AnnotationDrivenTx. It would be nice to have them back too.

[spring-projects-issues]

Chris Beams commented

This work is underway and should be merged into trunk shortly. See #12078 for an overarching issue that tracks other such changes e.g., annotation support for AspectJ auto-proxying, etc.

[spring-projects-issues]

Chris Beams commented

A @ComponentScan annotation was added in Spring 3.1 M1 as a declarative alternative to the new ComponentScanSpec implementation of FeatureSpecification. See Javadoc for usage instructions.