After returning to see the results of the main analysis about the situation:
get entity class, set method does
mapper.xml file resultMap, resultType other causes
Database data checking and validation problems found through the above do not exist
In question, including the code logic has also been checked several times. Really do not know where the problem lies, then went to see the root of the problem, detailed view of the resulting query returns a result, it was found that all the fields are null for the phenomenon is that there is a hump field names are named, and then automatically convert online access mybatis field hump named configuration. as follows:
# Enable hump naming mybatis.configuration.map-underscore-to-camel-case=true