JdbcSupportLoader throws AbstractMethodError on JDBC < 1.4 ---------------------------------------------------------- Key: HHH-5459 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5459 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.Beta2 Reporter: Stephane Epardaud When using a legacy JDBC driver before Java 1.4 I get the following exception: {noformat} Caused by: java.lang.AbstractMethodError: solid.jdbc.SolidDatabaseMetaData.getJDBCMajorVersion()I at com.mchange.v2.c3p0.impl.NewProxyDatabaseMetaData.getJDBCMajorVersion(NewProxyDatabaseMetaData.java:3726) at org.hibernate.engine.jdbc.JdbcSupportLoader.useContextualLobCreation(JdbcSupportLoader.java:78) at org.hibernate.engine.jdbc.JdbcSupportLoader.loadJdbcSupport(JdbcSupportLoader.java:52) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:121) at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:891) {noformat} Which is due to the fact that JdbcSupportLoader invokes DatabaseMetaData.getJDBCMajorVersion() which was introduced in Java 1.4. Would it be possible to check for the presence of this function so that we can keep using legacy drivers which in our case is the only way to keep working with this obsolete database (Solid)? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira