|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
I think it is easy to make C3P0 enough JDBC4 compliant to fix this with a simple patch in C3P0. The proxy class is generated by a code generator and i have run it with JDK 1.6. It has created the additional methods and it looks like that it should work well. I haven't tested it yet but it compiles.
Of course there are other places where it might crash sooner or later depending on changes in Hibernate. But at least this problem shouldn't stop you from using CP30 with 4.1.8+ . And maybe there will be a full JDBC4 version one day. The developer is aware that it is about time for a JDBC4 version. But I have the feeling that this might take some time