LazyInitTargetSourceCreator does not work in Java-based configuration [SPR-10508]

[spring-projects-issues]

Tobias Flohre opened SPR-10508 and commented

LazyInitTargetSourceCreator does not work in Java based configuration, as you can see in the example code in this forum thread: http://forum.springsource.org/showthread.php?125489-Configuration-BeanNameAutoProxyCreator-and-LazyInitTargetSourceCreator.

Interesting: a workaround is making the @Bean method for the lazy service object static.

---

Affects: 3.2.2

Attachments:

• AutoProxyLazyInitTest.java (3.01 kB)

Issue Links:

• InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiation not called for bean declared on JavaConfig [SPR-12140] #16754 InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiation not called for bean declared on JavaConfig ("depends on")
• InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiation called with wrong beanClass for bean declared on JavaConfig [SPR-12142] #16756 InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiation called with wrong beanClass for bean declared on JavaConfig ("depends on")
• javaconf + @Autowired + @PostConstruct + deep context import bug [SPR-8080] #12735 javaconf + @Autowired + @PostConstruct + deep context import bug

Referenced from: commits 8c9274e

2 votes, 5 watchers

[spring-projects-issues]

Antal Kiss commented

Please try to solve this in the next version.

[spring-projects-issues]

Arrault Fabien commented

This Issue is still present in Spring 4.0.6.

My tests shows that the problem is linked to the fact the lazy beans are created with JavaConfig, not to the fact that the LazyInitTargetSourceCreator or BeanNameAutoProxyCreator are created with JavaConfig.

I have created two issues for the root causes (in my opinion) of this problem : #16754 and #16756

The workaround works :
When the @Lazy @Bean method is static AND the @Configuration class does not implement any interface (because in this case the proxyTargetClass is forced to true on the ProxyFactory used), the proxy is created
If the @Configuration class do implement an interface, you must force the proxyTargetClass to true yourself on the BeanNameAutoProxyCreator to make it works
In both cases : the final proxyTargetClass setting if true .... while it may not be necessary

[spring-projects-issues]

Arrault Fabien commented

TestCase "AutoProxyLazyInitTest" added to reproduce different behaviours described in my comment.

In particular making the @Configuration implements ApplicationListener make ClassCastException when the proxyid bean is used (when the @Bean as the static modifier)

[spring-projects-issues]

Juergen Hoeller commented

It turns out that after fixing #16754, another issue gets in the way: The fix for #12735 prevents proper delegation to a target @Bean method for which a proxy has been registered already. This will be resolved along with this issue.

Juergen

[spring-projects-issues]

Juergen Hoeller commented

The #12735 case is now handled in ConstructorResolver itself: If the requested singleton magically appears after resolving its target factory bean, we throw an IllegalStateException which in turn gets caught by DefaultSingletonBeanRegistry and silently turned into the pre-existing singleton instance. This avoids special treatment in BeanMethodInterceptor and allows LazyInitTargetSource to work with @Bean methods as well.

Juergen

[spring-projects-issues]

Juergen Hoeller commented

This is available in the latest 4.1 snapshot now. If you have the chance, please give it a try today; the 4.1 GA release is scheduled for tomorrow European morning!

Juergen

[spring-projects-issues]

Arrault Fabien commented

I made a few tests and as far as I am concerned it works.

Fabien

[spring-projects-issues]

Juergen Hoeller commented

Great to hear - thanks for the quick turnaround!