MyBatis Invalid bound statement (not found) and Result Maps collection already contains value for ... Error resolution

I. Invalid bound statement (not found)

The use of MyBatis sometimes reported invalid bound statement (not found) This error, summarized below, there may be two cases are as follows:

The corresponding mapper.xml of 1.mybatis cannot find the corresponding named SQL or the name is inconsistent with the Mapper interface name.

The 2.xml file is the same as the interface name, but the configuration is missing from the MyBatis configuration file, and this error is reported.

Two. Result Maps collection already contains value for ...

A friend said, the MyBatis in the mappers attribute is removed, but, if the *mapper.xml file and mapper interface is not a package, is not removed, if there is no configuration in spring, then will be an error,

Sometimes the configuration is right, but still reported this mistake, and later did the experiment, will *mapper.xml file all deleted, rebuild the compilation, error, this is actually a strange problem, sometimes inevitably encounter.

MyBatis Invalid bound statement (not found) and Result Maps collection already contains value for ... Error resolution