This was not picked up as java.sql.Timestamp actually extends java.util.Date so there is actually no error reported etc.
The issue is that I would really expect a real java.util.Date rather than a Timestamp noting that they are logically different (even though Timestamp extends java.util.Date).
Could cause issues with equality tests etc.
Issue being the ScalarTypeUtilDate ... change isJdbcNative from true to false. This causes the automatic conversion to occur.
I am looking to change the ScalarType interface... to make them more functional in regards to JDBC reading from result sets and binding to preparedStatements.