Your question is confusing. Are you talking about a Java client which sees a JDBC driver that you'll provide, or a Java client which sees a CORBA interface that you'll provide?

Do you mean that you are trying to provide a JDBC driver for the client, which is actually going to be implemented as the stub for a CORBA server? (sort of a "JDBC-CORBA bridge"?) But then if this CORBA server is then going to access a database on behalf of the JDBC client, can your JDBC client just use the JDBC driver directly to the database, instead?

Or, are you saying you are trying to provide a CORBA server & IDL interface for the client, which internally uses JDBC to connect to a database, and returns results to the CORBA client through the IDL interface? If so, I would return DAO's (data access objects), not the ResultSet and Connection objects, because they are specific to JDBC!