|
From: Thomas R. <tho...@tr...> - 2005-10-02 21:09:02
|
We could also use the classloader for the connection to load any classes used for testing and for reflection - like conToUse.getClass().getClassLoader().loadClass (CONNECTION_CLASS_NAME); Thomas On Oct 2, 2005, at 4:58 PM, Thomas Risberg wrote: > > On Oct 2, 2005, at 4:43 PM, Juergen Hoeller wrote: > >> >> So our OracleLobHandler works on the new "oracle.jdbc.Connection" >> interface, >> while WebSphere seems to return an "oracle.jdbc.driver.Connection" >> that's >> not assignable to the "oracle.jdbc.Connection" interface. > > The class we test for is: > private static final String CONNECTION_CLASS_NAME = > "oracle.jdbc.OracleConnection"; > > In my tests any Oracle connection is assignable to this class as > long as they both come from the same classloader. > > Seems like the test is the problem here - maybe we should just test > for a class name that starts with "oracle.jdbc" > > Thomas > > > > |