The issue is not caused by the JDBC driver itself but by c3p0 which proxies all the JDBC calls. If a method introduced by JDBC4 (like PreparedStatement.setCharacterStream(int, Reader, long)) is called by hibernate, it will be called on the c3p0 proxy. The proxy not implementing the method, a java.lang.AbstractMethodError will be thrown.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Hi Romain,
The issue is not caused by the JDBC driver itself but by c3p0 which proxies all the JDBC calls. If a method introduced by JDBC4 (like PreparedStatement.setCharacterStream(int, Reader, long)) is called by hibernate, it will be called on the c3p0 proxy. The proxy not implementing the method, a java.lang.AbstractMethodError will be thrown.