用mabits查询结果传值给java实体类时,console报错:
org.mybatis.spring.MyBatisSystemException:nested exception is org.apache.ibatis.reflection.ReflectionException: Error instantiating class cn.com.bmsoft.astpserver.tag.dto.FrequentlyUseDto with invalid types () or values (). Cause: java.lang.NoSuchMethodException: cn.com.bmsoft.astpserver.tag.dto.FrequentlyUseDto.<init>()
at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:75)
at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:371)
at com.sun.proxy.$Proxy14.selectList(Unknown Source)
……
……
排查时确认已添加扫描路径:<context:component-scan base-package="cn.com.XXX" />;
也确认做好了字段映射,mapper.xml也没问题:
<select id="selectHistoryTagRecord" resultType="cn.com.bmsoft.astpserver.tag.dto.FrequentlyUseDto">
select tag_id tagId, tag_name tagName, value strValue, count, render_type renderType from TEMP_TAG_SEARCH_RECORD order by count desc
</select>
后来查看了一下实体类,发现之前测试手动添加数据的时候在映射类里添加了一个多参数的构造器:
controller:
FrequentlyUseDto entity2 = new FrequentlyUseDto(11, "区域", new Object[]{"03"}, "combotree");
映射类:
public class FrequentlyUseDto implements Serializable{
private static final long serialVersionUID = 1L;
private Integer tagId;
private String tagName;
private Object[] value;
private String renderType;
private String strValue;
public FrequentlyUseDto(Integer tagId, String tagName, Object[] value, String renderType) {
this.tagId = tagId;
this.tagName = tagName;
this.value = value;
this.renderType = renderType;
}
……
……
发现原来有参构造器的传值列表跟mabits返回的参数列表不对应。然后加上无参构造器或者删去不用的有参构造器就好了。也经此发现原来mabits映射的字段是由构造器放进映射类的,惭愧,自己对构造器理解有偏差,涨姿势了。