How does IBatis/MyBatis maps jdbcType=CURSOR to javaType=java.sql.ResultSet.

[Kumar Raja]

Hello All,

I have just started using MyBatis in our project and there are some existing xml mappers and codebase to start with. In those, I noticed that

<select id="getXXX" parameterType="map" resultMap="XXX_ResultMap" statementType="CALLABLE" fetchSize="50000" useCache="false">
		{ call YYY.XXX(

			#{selectCriteria, mode=IN, jdbcType=ARRAY, javaType=java.lang.Object},
			#{resultSet, mode=OUT, jdbcType=CURSOR, javaType=java.sql.ResultSet, resultMap=XXX_ResultMap},
			#{resultMessageText, mode=OUT, jdbcType=VARCHAR, javaType=java.lang.String}
		  )
		}
</select>

and in the code

Mapper mapper = session.getMapper(XXX.class);

inputs.put("selectCriteria", getCriteria());

mapper.getXXX(inputs);
			
Object resultMessage = inputs.get("resultMessageText");
if (resultMessage != null && !resultMessage.toString().trim().equals("Success.")) {
    throw new Exception();
}

Collection<XXXTYPE>results = (Collection<XXXTYPE>)inputs.get("resultSet");

My question is, "resultSet" which is declared as OUT for mode, jdbcType=CURSOR and javaType=java.sql.ResultSet, on what basis we are typecasting the resultset to Collection. java.util.Collection does not extend java.sql.ResultSet. So how is this being done. Also, why it is Collection only, why not a List.

Thanks