mybatis / spring-boot-starter

MyBatis integration with Spring Boot
Apache License 2.0
4.14k stars 1.79k forks source link

Error access org.mybatis.spring.SqlSessionFactoryBean #941

Closed tran4654040211 closed 10 months ago

tran4654040211 commented 10 months ago

I have a error when I run maven install Lifecycle. Error access org.mybatis.spring.SqlSessionFactoryBean In my spring boot app, I use: mybatis-spring: 3.0.3 version mybatis: 3.5.15 version spring-boot-starter-paren: 2.7.13 version java 8

Could any one can help me with this ? I can run my app and it work well in Intellij (Using jdk corretto 1.8) but I cann't run maven install Lifecycle. So, what is the problem ?

This is my batis config class

@Configuration @EnableTransactionManagement @MapperScan Class Mybatis Config {

@Bean public SqlSessionFactory sqlSessionFactory( @Qualifier(".."),Datasource, ApplicationContext ) { SqlSessionFactoryBean sqlSession = new SqlSessionFactoryBean() ; ... return sqlSession.getObject(); }

Sorry I cannot take some picture because security policy.

Thank you for your support.

harawata commented 10 months ago

If you use spring-boot-starter 2.7.x, you must use mybatis-spring-boot-starter 2.3.x. Please see the compatibility matrix. https://mybatis.org/spring-boot-starter/mybatis-spring-boot-autoconfigure/index.html#requirements

tran4654040211 commented 10 months ago

If you use spring-boot-starter 2.7.x, you must use mybatis-spring-boot-starter 2.3.x. Please see the compatibility matrix. https://mybatis.org/spring-boot-starter/mybatis-spring-boot-autoconfigure/index.html#requirements

Thank you, I will change and test

tran4654040211 commented 10 months ago

If you use spring-boot-starter 2.7.x, you must use mybatis-spring-boot-starter 2.3.x. Please see the compatibility matrix. https://mybatis.org/spring-boot-starter/mybatis-spring-boot-autoconfigure/index.html#requirements

So, I also have question why I can start my app by run main class in IntelliJ ?

harawata commented 10 months ago

There probably is an old JAR somewhere.

I'll assume the error is resolved.