多個springboot專案合併的問題總結
阿新 • • 發佈:2020-07-16
一.不同的包下存在同名的類名問題:
1.1 啟動過程中的錯誤:
(類似的其他報錯)
Caused by: org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'nameConflict' for bean class [xom.liuyun.beannameconflict.modelB.NameConflict] conflicts with existing, non-compatible bean definition of same name and class[xom.liuyun.beannameconflict.modelA.NameConflict] at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.checkCandidate(ClassPathBeanDefinitionScanner.java:348) ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE] at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:286) ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE] at org.springframework.context.annotation.ComponentScanAnnotationParser.parse(ComponentScanAnnotationParser.java:132) ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:284) ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:241) ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:198) ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:166) ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE] ... 13 common frames omitted。
1.2 報錯原因:
spring提供兩種beanName生成策略,基於註解的sprong-boot預設使用的是AnnotationBeanNameGenerator,它生成beanName的策略就是,取當前類名(不是全限定類名)作為beanName。
由此,如果出現不同包結構下同樣的類名稱,肯定會出現衝突。
1.3 解決辦法:
自己寫一個類實現org.springframework.beans.factory.support.BeanNameGeneraot介面
public class UniqueNameGenerator extends AnnotationBeanNameGenerator { @Override public String generateBeanName(BeanDefinition definition, BeanDefinitionRegistry registry) { //全限定類名 String beanName = definition.getBeanClassName(); return beanName; } }
在啟動類上加註解@ComponentScan(nameGenerator = UniqueNameGenerator.class)使剛才我們自定義的BeanName生成策略生效。
如下:
@SpringBootApplication @ComponentScan(nameGenerator = UniqueNameGenerator.class) public class BeanNameConflictApplication { public static void main(String[] args) { SpringApplication.run(BeanNameConflictApplication.class, args); } }
二.解決Mybatis提供的@Mapper注入bean的衝突
以上第一部分可以解決@Controller,@Service等Spring提供的bean注入的同名類衝突,@Mapper不是spring的註解,所以以上部分無法解決@Mapper注入bean的類衝突
解決辦法:
在啟動類上@MapperScan註解加入mapper的包名
@SpringBootApplication //全限定類名 @ComponentScan(nameGenerator = UniqueNameGenerator.class) @MapperScan(value={"com.grand.p1upgrade.mapper","com.grand.quickreaction.mapper","com.grand.springboottemplate.app.mapper","com.grand.springboottemplate.environment.mapper"},nameGenerator = UniqueNameGenerator.class) //@ServletComponentScan //要將Application類放在最外側,即包含所有子包 原因:spring-boot會自動載入啟動類所在包下及其子包下的所有元件. public class EnvironmentApplication { public static void main(String[] args) { SpringApplication.run(EnvironmentApplication.class, args); } //springcloud-前端跨域問題的解決方案全域性配置 @Bean public WebMvcConfigurer corsConfigurer() { WebMvcConfigurer webMvcConfigurer = new WebMvcConfigurer() { @Override public void addCorsMappings(CorsRegistry registry) { registry.addMapping("/**").allowedOrigins("*").allowCredentials(true).allowedMethods("*").maxAge(3600).allowedHeaders("*"); } }; return webMvcConfigurer; } }