Menu
▾
▴
springframework-developer
|
From: Juergen H. <ju...@in...> - 2005-10-02 19:11:26
|
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 |
|
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... |
|
From: Thomas R. <tho...@tr...> - 2005-10-02 20:11:06
|
I think the oracle.jdbc.driver.OracleConnection extends oracle.jdbc.OracleConnection so they should both work. The connection I get back from 10g is oracle.jdbc.driver.T4CConnection and it is assignable as well. Could this be a class loader issue? Thomas On Oct 2, 2005, at 3:20 PM, Duncan Mills wrote: > 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... > > > > ------------------------------------------------------- > 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 > > > |
|
From: Juergen H. <ju...@in...> - 2005-10-02 20:44:14
|
Actually, I mixed up the class names in my original mail: WebSphere returns an object of class "oracle.jdbc.driver.Connection" as underlying connection there, not an "oracle.jdbc.Connection" as expected by our OracleLobHandler. 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. This could indeed be a class loader issue: if the local "oracle.jdbc.Connection" interface has been loaded by a different class loader than the Connection handle returned by WebSphere... In principle, we could also relax the Connection type check in OracleLobHandler, as the Connection handle is just passed on via reflection anyway. That check is really just there to be able to throw a nice exception. But even if we relaxed that check, I guess we'd still run into a class loader issue: I'd expect the Oracle CLOB.createTemporary call to result in an internal ClassCastException within the driver implementation in this case... Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Thomas Risberg Sent: Sunday, October 02, 2005 10:12 PM To: spr...@li... Subject: Re: [Springframework-developer] OracleLobHandler on WebSphere 6.0 I think the oracle.jdbc.driver.OracleConnection extends oracle.jdbc.OracleConnection so they should both work. The connection I get back from 10g is oracle.jdbc.driver.T4CConnection and it is assignable as well. Could this be a class loader issue? Thomas On Oct 2, 2005, at 3:20 PM, Duncan Mills wrote: > 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... > > > > ------------------------------------------------------- > 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 > > > ------------------------------------------------------- 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 |
|
From: Thomas R. <tho...@tr...> - 2005-10-02 20:57:57
|
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
|
|
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 > > > > |
|
From: Juergen H. <ju...@in...> - 2005-10-02 21:15:02
|
Yes... but I guess checking for the name starting with "oracle.jdbc." would be fine. It's just about checking whether the passed-in Connection has any chance of getting accepted by CLOB.createTemporary(con, ...) so we don't really need a full type check there - just a basic sanity check. Juergen _____ From: spr...@li... [mailto:spr...@li...] On Behalf Of Thomas Risberg Sent: Sunday, October 02, 2005 11:10 PM To: spr...@li... Subject: Re: [Springframework-developer] OracleLobHandler on WebSphere 6.0 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 |
|
From: Juergen H. <ju...@in...> - 2005-10-03 07:58:35
|
Odd mail order here... As I wrote in my actually latest mail, I have changed OracleLobHandler to use a post-invocation ClassCastException check; already committed to CVS. Juergen _____ From: spr...@li... [mailto:spr...@li...] On Behalf Of Juergen Hoeller Sent: Sunday, October 02, 2005 11:15 PM To: spr...@li... Subject: Re: [Springframework-developer] OracleLobHandler on WebSphere 6.0 Yes... but I guess checking for the name starting with "oracle.jdbc." would be fine. It's just about checking whether the passed-in Connection has any chance of getting accepted by CLOB.createTemporary(con, ...) so we don't really need a full type check there - just a basic sanity check. Juergen _____ From: spr...@li... [mailto:spr...@li...] On Behalf Of Thomas Risberg Sent: Sunday, October 02, 2005 11:10 PM To: spr...@li... Subject: Re: [Springframework-developer] OracleLobHandler on WebSphere 6.0 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 |
|
From: Juergen H. <ju...@in...> - 2005-10-02 21:12:47
|
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 |
|
From: Mark St G. <stg...@ca...> - 2005-10-02 20:41:36
|
I am running Webpshere 6, with Hibernate 3, Spring 1.2.5 and Oracle 10g....
I also get back a: oracle.jdbc.driver.T4CConnection
assertTrue(oracle.jdbc.OracleConnection.class.isAssignableFrom(conn.getClass()));
assertTrue(oracle.jdbc.driver.OracleConnection.class.isAssignableFrom(conn.getClass()));
And it looks to be assignable...
Cheers
Mark
Thomas Risberg
<thomas.risberg@t
ridb.com> To
Sent by: spr...@li...
springframework-d rceforge.net
eveloper-admin@li cc
sts.sourceforge.n
et Subject
Re: [Springframework-developer]
OracleLobHandler on WebSphere 6.0
10/02/2005 03:11
PM
Please respond to
springframework-d
eveloper
I think the oracle.jdbc.driver.OracleConnection extends
oracle.jdbc.OracleConnection so they should both work. The
connection I get back from 10g is oracle.jdbc.driver.T4CConnection
and it is assignable as well. Could this be a class loader issue?
Thomas
On Oct 2, 2005, at 3:20 PM, Duncan Mills wrote:
> 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...
>
>
>
> -------------------------------------------------------
> 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
>
>
>
-------------------------------------------------------
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
|
|
From: Juergen H. <ju...@in...> - 2005-10-02 21:12:10
|
So it's probably indeed a class loader issue... Maybe the reporter had
ojdbc14.jar at both the server and the application level.
Juergen
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Mark St Godard
Sent: Sunday, October 02, 2005 10:33 PM
To: spr...@li...
Subject: Re: [Springframework-developer] OracleLobHandler on WebSphere 6.0
I am running Webpshere 6, with Hibernate 3, Spring 1.2.5 and Oracle 10g....
I also get back a: oracle.jdbc.driver.T4CConnection
assertTrue(oracle.jdbc.OracleConnection.class.isAssignableFrom(conn.getClass
()));
assertTrue(oracle.jdbc.driver.OracleConnection.class.isAssignableFrom(conn.g
etClass()));
And it looks to be assignable...
Cheers
Mark
Thomas Risberg
<thomas.risberg@t
ridb.com> To
Sent by: spr...@li...
springframework-d rceforge.net
eveloper-admin@li cc
sts.sourceforge.n
et Subject
Re: [Springframework-developer]
OracleLobHandler on WebSphere 6.0
10/02/2005 03:11
PM
Please respond to
springframework-d
eveloper
I think the oracle.jdbc.driver.OracleConnection extends
oracle.jdbc.OracleConnection so they should both work. The connection I get
back from 10g is oracle.jdbc.driver.T4CConnection and it is assignable as
well. Could this be a class loader issue?
Thomas
On Oct 2, 2005, at 3:20 PM, Duncan Mills wrote:
> 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...
>
>
>
> -------------------------------------------------------
> 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
>
>
>
-------------------------------------------------------
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
-------------------------------------------------------
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
|
|
From: Thomas R. <tho...@tr...> - 2005-10-02 20:50:49
|
Must be a classloader issue. Just tested by forcing a different classloader for the connection and the connectionClass that is used to test assignability - it returns false with different classloader. Maybe the context classloader pick up a different class on its path. Thomas On Oct 2, 2005, at 4:11 PM, Thomas Risberg wrote: > I think the oracle.jdbc.driver.OracleConnection extends > oracle.jdbc.OracleConnection so they should both work. The > connection I get back from 10g is oracle.jdbc.driver.T4CConnection > and it is assignable as well. Could this be a class loader issue? > > Thomas > > > On Oct 2, 2005, at 3:20 PM, Duncan Mills wrote: > > >> 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... >> >> >> >> ------------------------------------------------------- >> 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 >> >> >> >> > > > > ------------------------------------------------------- > 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 > > > |
