New typehandler implementation is not called during select statment. about mybatis HOT 4 CLOSED

If the executor is attempting to find your typeHandler with a null JDBC type, 
it's
possible that the result mapping isn't specifying the jdbcType.  For example:

<result ... javaType="String" jdbcType="VARCHAR"> 

...would look up java.lang.String and Types.VARCHAR in the TYPE_HANDLER_MAP.  
But...

<result ... javaType="String">

...would look up java.lang.String and null in the TYPE_HANDLER_MAP.

You can register your date typehandler without specifying the jdbcType so that 
it
applies to ALL date types, regardless of the column in the database.  So using 
your
example:

<typeHandler javaType="java.util.GregorianCalendar" 
             handler="somepackage.GregorianCalendarTypeHandler"/>

If you feel that this is incorrect, then maybe file a unit test or another 
example
demonstrating the failure.

Cheers,
Clinton

Hi Clinton!

Thank you for your answer.

As I see the iBatis can figure out the mappings so currently I'm not using any 
result
mapping for my statement. Is this a mistake on my side? I think when the 
statement
doesn't defines a resultMap (it uses instead a resultType) the
ResultSetMetaData#getcolumnType() should be used to figure out the column's 
JDBC type.

I have jared up and uploadad a dummy maven project that contains the POJOs and 
the
mapping that I'm using to show you what I am doing exactly.

Regards, István.

I've experienced a similar issue to the described above.

In my case (described also here: 
http://stackoverflow.com/questions/20122157/mybatis-custom-typehandler-not-execu
ted-when-put-in-result-tag/) I had a custom typeHandler attached to <result> 
tag:

<result property="SERVICES_XML" javaType="string" jdbcType="CLOB" 
typeHandler="com.foo.bar.OracleClobTypeHandler" />

That didn't work unless I explicitly specified "column" attribute for the above 
<result> tag. 
If this is the expected behaviour, it definitely needs to be documented.