在解决mybatis-plus分页失效时遇到一个很诡异的问题,当时分页不生效时,添加如下配置
/**
* 配置mybatis分页插件
*
* @return MybatisPlusInterceptor
*/
@Bean
public MybatisPlusInterceptor paginationInnerInterceptor() {
MybatisPlusInterceptor interceptor = new MybatisPlusInterceptor();
interceptor.addInnerInterceptor(new PaginationInnerInterceptor());
return interceptor;
}
添加后运行项目,发现分页还是不生效,于是就增加SqlSessionFactory配置,把分页拦截器手动设置进去
@Bean
public SqlSessionFactory sqlSessionFactory() throws Exception {
MybatisSqlSessionFactoryBean sqlSessionFactoryBean = new MybatisSqlSessionFactoryBean();
sqlSessionFactoryBean.setDataSource(dataSource());
//分页total为0,在数据源显示配置mybatis插件
MybatisConfiguration configuration = new MybatisConfiguration();
configuration.setMapUnderscoreToCamelCase(true);
configuration.setDefaultEnumTypeHandler(EnumOrdinalTypeHandler.class);
sqlSessionFactoryBean.setConfiguration(configuration);
sqlSessionFactoryBean.setPlugins(new Interceptor[]{paginationInnerInterceptor()});
return sqlSessionFactoryBean.getObject();
}
SqlSessionFactory配置完成后,运行项目,诡异的事情出现了,报如下错误
当时很纳闷,因为没有配置SqlSessionFactory之前是能查询数据的,配置完之后就报这个错误了。思考了一会可能是mapper.xml文件没有扫描到,检查配置文件也存在
mybatis-plus:
mapper-locations: classpath*:com/xx/xx/xx/xx/*.xml
最后发现我创建的MybatisSqlSessionFactoryBean对象是一个新的值,他里面mapperLocations是默认的配置,要把配置文件的配置重新设置进去。最终的MybatisSqlSessionFactoryBean配置如下
@Autowired
private MybatisPlusProperties mybatisPlusProperties;
@Bean
public SqlSessionFactory sqlSessionFactory() throws Exception {
MybatisSqlSessionFactoryBean sqlSessionFactoryBean = new MybatisSqlSessionFactoryBean();
sqlSessionFactoryBean.setDataSource(dataSource());
//分页total为0,在数据源显示配置mybatis插件
MybatisConfiguration configuration = new MybatisConfiguration();
configuration.setMapUnderscoreToCamelCase(true);
configuration.setDefaultEnumTypeHandler(EnumOrdinalTypeHandler.class);
sqlSessionFactoryBean.setConfiguration(configuration);
sqlSessionFactoryBean.setPlugins(new Interceptor[]{paginationInnerInterceptor()});
Resource[] resources = mybatisPlusProperties.resolveMapperLocations();
sqlSessionFactoryBean.setMapperLocations(resources);
return sqlSessionFactoryBean.getObject();
}
重新运行项目后不在出现问题