Cause: org. apache. ibatis. builder. Builderexception: error parsing SQL mapper configuration problem analysis

Errors are common , There are too many reasons for the problem , Here is how to find

Cause: org.apache.ibatis.builder.BuilderException: Error parsing SQL Mapper Configuration. 
Cause: org.apache.ibatis.builder.BuilderException: Error resolving class.
Cause: org.apache.ibatis.type.TypeException: Could not resolve type alias ''.  
Cause: java.lang.ClassNotFoundException: Cannot find class: 

1. First of all, when making such a mistake , The console will output you more detailed error information to tell you what mistakes you have made ：

   The first two lines tell you Mapper Configuration Unable to resolve . Okay , The probability is in your configuration Mapper Of xml In file （ I was in mybatis The configuration of xml in ）

2. Then the third line tells you that you can't solve ’ ’ This type of ：
   　　’ ’ What kind of ？ The type of a quotation mark ？ Obviously xml I didn't write in some places , What remains is empty ‘ ’. Okay , You can see xml In some places , You can find that you really haven't written

---

Empathy ： In the analysis of a

Cause: org.apache.ibatis.builder.BuilderException: Error parsing SQL Mapper Configuration. 
Cause: org.apache.ibatis.builder.BuilderException: Error resolving class.
Cause: ....Unknown DataSource property: driverClass
....

1. The meaning of the first two sentences is the same , The configuration file cannot be resolved . I'll just skip to configuration mapper Of xml In the
2. The third sentence is unrecognizable DataSource label ：property label （driverClass）
Be careful ： Here I use direct jdbc The driver account password and other four tags are directly written in xml in , There is no way to use configuration files . So here property It should be ordinary driver：（ If you are a configuration file , Please keep consistent with the configuration file ）