You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running an application with mybatis-spring-boot-starter version 3.0.3, mybatis-spring 3.04 and mybatis version 3.5.16.
On startup I get an error warning No MyBatis mapper was found in '[....]' package" which is unexpected for me. It is true that I have not defined any mapper classes because I have defined all mappings via XML configuration files. And I make these files available via the mybatis.mapper-locations=/mapperXml/*_Mapper.xml configuration. Everything works fine, thus no need to print a warning here.
I wonder if I can suppress the warning. There is a method setPrintWarnLogIfNotFoundMappers but no configuration property in the mybatis-spring-boot-starter to set the value (at least I did not found any).
I would appreciate it if the warning was not displayed (as the mapper files are not necessary) or if this warning could at least be suppressed. However, I don't see this as a bug but rather as a minor improvement.
The text was updated successfully, but these errors were encountered:
I am running an application with mybatis-spring-boot-starter version 3.0.3, mybatis-spring 3.04 and mybatis version 3.5.16.
On startup I get an error warning
No MyBatis mapper was found in '[....]' package"
which is unexpected for me. It is true that I have not defined any mapper classes because I have defined all mappings via XML configuration files. And I make these files available via themybatis.mapper-locations=/mapperXml/*_Mapper.xml
configuration. Everything works fine, thus no need to print a warning here.The warning message probably comes from the ClassPathMapperScanner.
I wonder if I can suppress the warning. There is a method setPrintWarnLogIfNotFoundMappers but no configuration property in the mybatis-spring-boot-starter to set the value (at least I did not found any).
I would appreciate it if the warning was not displayed (as the mapper files are not necessary) or if this warning could at least be suppressed. However, I don't see this as a bug but rather as a minor improvement.
The text was updated successfully, but these errors were encountered: