ClassCastException from OraclePreparedStatement.setArrayInternal() method

Question

The following code throws a ClassCastException from oracle.jdbc.driver.OraclePreparedStatement.setArrayInternal() method line# 5886 when cs.setArray() is executed.
Connection conn = getConnection(); // Returns a java.sql.Connection instance
CallableStatement cs = conn.prepareCall(queryString);
cs.setArray(1, new UsnArray(usns)); // UsnArray implements java.sql.Array
cs.registerOutParameter(2, Types.INTEGER);
cs.execute();
This works if I create the CallableStatement on an oracle.jdbc.driver.OracleConnection instance and use an oracle.sql.ARRAY instance in the setArray() method call. A JDBC-compliance driver shouldn't be expecting the applications to use driver-specific classes. The application can pass any instance of type java.sql.Array in the setArray() method call.
Is this a bug in the driver?
Driver information from ojdbc14.jar manifest.mf file:
Manifest-Version: 1.0
Specification-Title: Oracle JDBC driver classes for use with JDK14
Sealed: true
Created-By: 1.4.2_08 (Sun Microsystems Inc.)
Implementation-Title: ojdbc14.jar
Specification-Vendor: Oracle Corporation
Specification-Version: Oracle JDBC Driver version - "10.2.0.2.0"
Implementation-Version: Oracle JDBC Driver version - "10.2.0.2.0"
Implementation-Vendor: Oracle Corporation
Implementation-Time: Tue Jan 24 08:55:21 2006
Name: oracle/sql/converter/
Sealed: false
Name: oracle/sql/
Sealed: false
Name: oracle/sql/converter_xcharset/
Sealed: false
--------------------------------------------------------------------------------------------------

Answer 1

Let me elaborate on your last two replies: it doesn't matter what other drivers support; it doesn't matter what your "intention" was; all that matters is whether the implementation adheres to the specification or not. If it is not, it is not compliant to the specification (period). It is a very strong statement to say that "You must use oracle.sql.ARRAY." I'm not quite sure you understand the meaning and motivation behind standards like JDBC and J2EE and standards bodies like ANSI. This is very obvious when you say that "This is a limitation of the expressiveness of the Java type system."
If you think the JDBC compliance only mandates that "A driver is only required to accept a value that is of the concrete class defined by the driver," which is not mentioned anywhere in the spec anyway, then Sun would have simply defined the setArray method as "public void setArray(int i, oracle.sql.ARRAY x)" (one for each driver available) instead of saying "public void setArray(int i, java.sql.Array x)". It also clearly says that if a specification is not supported by a driver, in which case it must be specified in the DatabaseMetaData, the driver must throw a SQLEception. Bur your claim completely contradicts everything. You can also refer links like this on the Web: http://archives.postgresql.org/pgsql-jdbc/2003-07/msg00294.php.
I don't know what you mean by "The JDBC spec is not as precise as it could be." The relevant requirements have been clearly stated throughout Chapter 13 “Statements” and in Appendix B "Data Type Conversion Tables" in JDBC 3.0 spec (Chapter 8 Section 3 "Arrays" in JDBC 2.1 spec).
A JDBC driver may provide underlying data source-specific features in addition to those mandated by the JDBC specification. Applications that try to take advantage these additional features may decide to “stick” with a specific driver and import driver-specific classes. But these additional features cannot substitute the basic requirements.