@ComponentScan does not allow for registering beans with lazy initialization [SPR-10459]

[spring-projects-issues]

Michał B opened SPR-10459 and commented

When configuration is specified like this, ComponentScan ignores annotation @Lazy and every bean found in "org.dzik" is created eagerly.

@Configuration
@Lazy
@ComponentScan("org.dzik")
public class BasicConfiguration {

}

---

Affects: 3.2.2

Attachments:

• ComponentScan.java (7.11 kB)
• ComponentScanAnnotationParser.java (6.12 kB)

Issue Links:

• Doc: Lazy context is not validated on creation [SPR-11495] #16120 Doc: Lazy context is not validated on creation

4 votes, 8 watchers

[spring-projects-issues]

Jim LoVerde commented

I'm having this problem with version 3.1.3 as well. It looks like this should be fairly easy to implement in the Spring source code. Basically add an attribute to the ComponentScan annotation called lazyInit with a default value of false. And then in ComponentScanAnnotationParser.parse, right after instantiating the ClassPathBeanDefinitionScanner (or via it's constructor) you can update it's beanDefinitionDefaults with the value from the ComponentScan annotation.

Unfortunately without modifying the Spring source, adding this change looks to be painful. The closest "hook" I can find seems to be to override the definition of the org.springframework.context.annotation.internalConfigurationAnnotationProcessor bean with a copy/subclass of ConfigurationClassPostProcessor, which creates the ConfigurationClassParser in processConfigBeanDefinitions, which constructs the ComponentScanParser in it's constructor.

Otherwise, you have to resort to importing XML that does the component scan for you, which is unfortunate.

[spring-projects-issues]

Jim LoVerde commented

here are modified files from spring-context 3.1.3.RELEASE that support lazyInit by default for @ComponentScan beans

[spring-projects-issues]

Jim LoVerde commented

I've attached the modified source files that seem to allow this to work on my local project.

[spring-projects-issues]

Jean-Pierre Bergamin commented

Any reason why the fix from Jim has not been integrated yet? This feature is really missing!

[spring-projects-issues]

Juergen Hoeller commented

This is finally making it into 4.1 now. Sorry that it took so long...

Juergen