前面的三篇文章写下来,发现一个问题,还是需要在关键类上使用@Component注解才能完成Spring对我们的Fisher框架初始化。那么,怎么去掉@Component注解呢?这是一个值得探讨的问题。根据前面的套路,我们发现一个有趣的现象。无论哪种方式(XML配置或是注解),最后都调用了ClassPathMapperScanner类的scan()方法(其实是父类ClassPathBeanDefinitionScanner类中声明的,ClassPathMapperScanner类重写了doScan()方法完成后续步骤)。所以,我们来看看doScan()方法都被谁使用了:
我们要实现的靠一个@MapperScan注解实现自动配置是在SpringBoot中完成的。所以我们的目标锁定第三个方法的实现类,代码如下:
public static class AutoConfiguredMapperScannerRegistrar
implements BeanFactoryAware, ImportBeanDefinitionRegistrar, ResourceLoaderAware {
private BeanFactory beanFactory;
private ResourceLoader resourceLoader;
@Override
public void registerBeanDefinitions(AnnotationMetadata importingClassMetadata, BeanDefinitionRegistry registry) {
logger.debug("Searching for mappers annotated with @Mapper");
ClassPathMapperScanner scanner = new ClassPathMapperScanner(registry);
try {
if (this.resourceLoader != null) {
scanner.setResourceLoader(this.resourceLoader);
}
List<String> packages = AutoConfigurationPackages.get(this.beanFactory);
if (logger.isDebugEnabled()) {
for (String pkg : packages) {
logger.debug("Using auto-configuration base package '" + pkg + "'");
}
}
scanner.setAnnotationClass(Mapper.class);
scanner.registerFilters();
scanner.doScan(StringUtils.toStringArray(packages));
} catch (IllegalStateException ex) {
logger.debug("Could not determine auto-configuration package, automatic mapper scanning disabled." + ex);
}
}
@Override
public void setBeanFactory(BeanFactory beanFactory) throws BeansException {
this.beanFactory = beanFactory;
}
@Override
public void setResourceLoader(ResourceLoader resourceLoader) {
this.resourceLoader = resourceLoader;
}
}
确认过眼神,是对的线索,顿时一种熟悉的感觉扑面而来。那么新的问题又出现了,如果只是这样,那和之前有啥区别?还是摆脱不了@Component注解啊!答案就是SpringBoot中的Spring Factories机制了!(要了解它可以参考一下这篇文章:https://blog.csdn.net/xjl465008408/article/details/80869864?utm_source=blogxgwz0)
福利时间又到了!亲测!
1.在与src同级的路径下新建“META_INF”文件夹,然后创建spring.factory文件
2.把下面的文本复制进去:
# Auto Configure
org.springframework.boot.autoconfigure.EnableAutoConfiguration=\
com.fish.FisherScannerRegistrar
到这里,@Component注解可以扔掉啦!