|
From: Duncan M. <dun...@or...> - 2005-10-02 19:20:38
|
Juergen, There has been some refactoring in the Oracle JDBC drivers (as of the 10g version) so the correct class is now oracle.jdbc.Connection. oracle.jdbc.driver.Connection is deprecated but should still be supported until version 11 of the database. I'm not sure if that's the cause of the problem here but it's probably more than coincidental.. Duncan Juergen Hoeller wrote: >We have a report about an issue with Spring's OracleLobHandler on WebSphere >6.0: >http://opensource2.atlassian.com/projects/spring/browse/SPR-1317 > >Our WebSphereNativeJdbcExtractor seems to work, actually. It's rather that >WebSphere returns an object of class "oracle.jdbc.Connection" as underlying >connection there, not an "oracle.jdbc.driver.Connection" - as expected by >our OracleLobHandler, according to the Oracle 9i+ JDBC API. > >Could this be caused by a different Oracle driver that WebSphere uses, at >least in that specific scenario? Maybe it uses an older Oracle driver that >doesn't support the "oracle.jdbc.driver" package yet? Has anybody ever >encountered this, no matter whether on WebSphere or not? > >It would be great if someone with access to a WebSphere 6.0 + Oracle >installation could give this a try and see whether there's a way to solve >the issue... > >Juergen > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > -- Regards Duncan Mills Senior Principal Product Manager Oracle Application Development Tools Dun...@or... |