LoadTimeWeaverAware beans are consistently being created early for JPA weaving to work reliably

Reverted change for @Bean methods that declare FactoryBean as their return type: The effects of trying to create the FactoryBean to find out about its implementation type are too far-reaching. It's better to recommend declaring a specific return type in the method signature if you want the container to specifically react to your implementation type.

Issue: SPR-9857
This commit is contained in:
Juergen Hoeller
2012-10-12 23:31:12 +02:00
committed by unknown
parent 0af9244571
commit 3cf5572ee8
3 changed files with 3 additions and 7 deletions

View File

@@ -590,10 +590,6 @@ public abstract class AbstractAutowireCapableBeanFactory extends AbstractBeanFac
}
}
}
if (FactoryBean.class.equals(beanClass) && mbd.isSingleton() &&
(typesToMatch.length > 1 || (typesToMatch.length == 1 && !typesToMatch[0].equals(FactoryBean.class)))) {
return getSingletonFactoryBeanForTypeCheck(beanName, mbd).getClass();
}
return beanClass;
}