By default, Spring beans are scoped singleton, meaning there’s only one instance for the whole application context. For most applications, this is a sensible default; then sometimes, not so much. This may be the case when using a custom scope, which is the case, on the product I’m currently working on. I’m not at liberty to discuss the details further: suffice to say that it is very painful to configure each and every needed bean with this custom scope.
Since being lazy in a smart way is at the core of developer work, I decided to search for a way to ease my burden and found it in the BeanFactoryPostProcessor class.
It only has a single method - postProcessBeanFactory(), but it gives access to the bean factory itself (which is at the root of the various application context classes).
From this point on, the code is trivial even with no prior experience of the API:
public class PrototypeScopedBeanFactoryPostProcessor implements BeanFactoryPostProcessor {
@Override
public void postProcessBeanFactory(ConfigurableListableBeanFactory factory) throws BeansException {
for (String beanName : factory.getBeanDefinitionNames()) {
BeanDefinition beanDef = factory.getBeanDefinition(beanName);
String explicitScope = beanDef.getScope();
if ("".equals(explicitScope)) {
beanDef.setScope("prototype");
}
}
}
}The final touch is to register the post-processor in the context . This is achieved by treating it as a simple anonymous bean:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<bean class="ch.frankel.blog.spring.scope.PrototypeScopedBeanFactoryPostProcessor" />
</beans>Now, every bean which scope is not explicitly set will be scoped prototype.
Sources for this article can be found attached in Eclipse/Maven format.