issue typecasting java.sql.CallableStatement into oracle.jdbc.driver.OracleCallableStatement

[nandini lagunia]

Hi,

I have written a test class in which I've typecasted java.sql.CallableStatement into oracle.jdbc.driver.OracleCallableStatement and it's works fine.
the code is:-

         java.sql.Connection con = deleteCustomerPoolConnectionFactory.getDBConnection();
   		   java.sql.CallableStatement cs = con.prepareCall("{call delcust_order_byworkorder_mul(?,?,?)}");
   		   oracle.sql.ArrayDescriptor descriptor =oracle.sql.ArrayDescriptor.createDescriptor("WORKORDERARRAY", con );
   		   oracle.sql.ARRAY outArr = new oracle.sql.ARRAY( descriptor, con, workOrderNumberArr); 
   		   [b]((oracle.jdbc.driver.OracleCallableStatement)cs).setARRAY(1, outArr);  [/b]    //line #456

When I put the code in an ejb business method and invoke the method, it throws java.lang.ClassCastException at line #456

I don't have any clue why it's behaving like this. Will anybody help me???

Thanks in advance.

[Jan Cumps]

Do you get a OracleCallableStatement compatible object from your con.prepareCall()?

[nandini lagunia]

Hi,

The same piece of code works fine in the standalone utilty.

OracleCallableStatement interface implements java.sql.CallableStatement()here so we can very well
go for explicit casting.

Don't you think so?

[nandini lagunia]

con.prepareCall() returns java.sql.CallableStatement.

[Jan Cumps]

nandini lagunia wrote:con.prepareCall() returns java.sql.CallableStatement.

Do you know the exact class that it returns in your case,
both for the standalone and not so standalone use case?

you can use the getName() method on cs in both cases. Wonder if there is a difference in the two cases...