]
Steve Ebersole commented on HHH-2412:
-------------------------------------
Ahmet, better solutions to the ResultSetWrapper are (1) to utilize AOP and pointcuts
against the JDBC driver or (2) to use instrucmentation of those JDBC drivers in the cases
where the JDBC driver suffers from these performance issues. That's obviously not
something Hibernate can provide though.
Hibernate 3 cannot be compiled under JDK 6
------------------------------------------
Key: HHH-2412
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2412
Project: Hibernate Core
Issue Type: Task
Components: core
Affects Versions: 3.2.1, 3.2.2
Environment: windows xp, JDK 6
Reporter: Ahmet A. Akin
Fix For: 3.6
Hibernate code cannot be compiled under JDK 6. Problems and possible solutions:
1- org.hibernate.jdbc.ResultSetWrapper implements ResultSet. But in Java 6, there are big
changes in Resultset interface, and maybe 20+ more methods needs to be implemented in the
ResultSetWrapper class. i would suggest eliminating this wrapper class once and for all,
because it is only used in one method (in ColumnNameCache, getIndexForColumnName method)
and i dont think there is a justification for using that wrapper class.
2- org.hibernate.lob.SerializableBlob needs to implement new Blob interface methods:
public void free() throws SQLException;
public InputStream getBinaryStream(long pos, long length) throws SQLException
But, if this class is publicly accesible or used by API's back compatibility issues
needs to be checked.
3- Same as number 2, org.hibernate.lob.BlobImpl class needs to implement new Blob
methods.
4- org.hibernate.lob.SerializableClob class needs to implent new Clob methods.
5- org.hibernate.lob.ClobImpl , same as 4.
In fact, Java 6 has a lot of JDBC improvements, maybe a java6 special extra package can
be created., but that is a whole different issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: