Re: [Springframework-developer] OracleLobHandler on WebSphere 6.0

[Juergen H. <ju...@in...>]

Yes, simply relaxing that check might already help. It's still a class
loader issue, but relaxing that check might make our OracleLobHandler work
despite the presence of that CL issue.
 
Juergen
 

  _____  

From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Thomas Risberg
Sent: Sunday, October 02, 2005 10:59 PM
To: spr...@li...
Subject: Re: [Springframework-developer] OracleLobHandler on WebSphere 6.0



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