For what it's worth, the newest Oracle JDBC drivers (12.1.0.1.0) no longer need dealing with this issue, since the proprietary Oracle batching model has been deprecated in favor of the standard JDBC batch update API. The new implementation correctly returns the update counts for the standard batch updates, so this should no longer be an issue. We've tested this and it seems to work fine.

Take into account that 12.1 drivers should work with 11g and 10g databases just fine. For older Oracle DB versions, you should check the JDBC driver compatibility matrix provided by Oracle.

See section 21 of the attached Oracle JDBC driver docs for version 12.1.0.1.0:
Note: Starting from Oracle Database 12c Release 1 (12.1), Oracle update batching is deprecated. Oracle recommends that you use standard JDBC batching instead of Oracle update batching.