How to understand the problem based on MapperXML scanning

This article focuses on "how to understand the problem based on MapperXML scanning", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to understand the problems based on MapperXML scanning.

Catalogue

Problems with MapperXML scanning

1. If you put XML under the java directory

2. If you put it under resources, configure it under .properties.

Description

Mybatis automatically scans XML files to fill in pits

Problem with MapperXML scanning 1. If you put XML in the java directory

You need to configure the path in the pom package. Or it can't be scanned.

2. If you put it under resources, configure the instructions under .properties.

Mapper Annotation Profil

@ MapperScan

Function: automatically add @ mapper to the mapper class under the corresponding mapper

Single packet

@ MapperScan (basePackages = "com.jimi.**.mapper")

Multiple packages

@ MapperScan ({"com.kfit.demo", "com.kfit.user"})

If the mapper class is not under a package or subpackage that the Spring Boot main program can scan, you can configure it as follows

@ MapperScan ({"com.kfit..mapper", "org.kfit..mapper"}) mybatis automatically scans XML files to fill holes

New XXDao.java has been named by XXDao.xml. Note the naming rules for mybatis automatic scan.

For example, xml whose path ends with Dao will be included in the scan, otherwise mybatis will report an error

At this point, I believe you have a deeper understanding of "how to understand the problem based on MapperXML scanning". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!