Re: CLOB problem in JAVA

Hi, yes. This is because Oracle did the amateurish thing of making a lot of it's nonstandard extensions to JDBC without making Interfaces for the extra calls, and also exposing methods with deceptive signatures. In this case the createTemporary() method *says* it takes a java.sql.Connection, which the WebSphere wrapper *is*, but the method *really* needs a direct naked oracle driver connection because somewhere deeper in the internals, it's casting the connection to a concrete oracle class to be able to call one of those nonstandard connection methods.

    Besides yelling at Oracle, your only real recourse is to stick to only standard JDBC calls, or use only direct Oracle connections for these calls, outside the scope, purview, and wrapping of WebSphere. WebSphere might have a call you could make in this context to get a handle to the underlying real oracle connection, in which cas you could pass that to the Clob call. I know BEA's WebLogic does...
Joe Weinstein at BEA Systems Received on Tue Jul 26 2005 - 00:47:53 CEST