Recently took over a project, using the framework is springboot+mybatis;
Where the persistence layer is integrated using MyBatis, SQL is configured in the Mapper.xml file;
And then, sometimes when it comes to new features, when adding new SQL logic to an XML file, there are some mistakes that can be caused by negligence or hand errors.
The concrete manifestation is: Eclipse's console has been in the fast brush log, also did not see what the error thing, is to brush some loading class file content;
Baidu later said that the XML configuration file is wrong, there are some articles is to go to the source code in a wrong place to increase the breakpoint, but every time after adding a break point after the start of no entry into the breakpoint at all;
Finally, use a common bug-finding method:
Rule of law: Comment out your newly modified content in turn, and then gradually locate the problem point, simple and rude, but very useful!
Here first, because I do not give priority to this method every time ....
The Spring Boot MyBatis project has been started after the bug fix that brushes the log ...