BeanPostProcessor won't ever get proxied bean in case of circular references in the bean [SPR-13163]

[spring-projects-issues]

Jan Novotný opened SPR-13163 and commented

BeanPostProcessors will obtain reference to unwrapped bean instead of proxy class that handles (for example) transaction attributes of the bean. This happens only for beans that have circular bean references in them.

Steps to reproduce:

1. load application context with proxy-exporting-example.xml file (correct packages in it)
2. add PublicInterfacePostProcessor in it
3. watch it crash :)

One of the beans will come as proxy to the post processor, the other one in unwrapped shape. This happens despite of BeanFactory has both beans in singletons repository proxied.

Workaround for this bug is to pass BeanFactory to the BeanPostProcessor class and do this:

{{@Override
public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {
if(bean instanceof PublicInterface) {
Advised proxy = beanFactory.getBean(beanName, Advised.class);
}
return bean;
}}}

---

Affects: 4.1.6

Attachments:

• proxy-exporting-example.xml (847 bytes)
• PublicInterfacePostProcessor.java (1.10 kB)
• TestServiceBean1.java (664 bytes)
• TestServiceBean2.java (664 bytes)

[spring-projects-issues]

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.