Oracle Database client libraries for Java now on Maven Central

Oracle has published its Oracle Database JDBC client libraries on Maven Central. From now on you can find Oracle Database related jar files under the com.oracle.database group id. You will find all libraries from version 11.2.0.4 (e.g. ojdbc6) to 19.3.0 (e.g. ojdbc10).

Going forward, Oracle will use Maven Central as one of the primary distribution mechanisms for Oracle Database Java client libraries, meaning that you will also be able to find new versions of these libraries on Maven Central in the future.

To get the latest Oracle Database JDBC driver, use the following dependency GAV in your Maven POM file:

<dependency> <groupId>com.oracle.database.jdbc</groupId> <artifactId>ojdbc10</artifactId> <version>19.3.0.0</version></dependency>

The com.oracle.database group id has the following subgroups:

  • oracle.database.jdbc: this group contains all JDBC libraries
    • ojdbc[N].jar:

      The Oracle Database JDBC driver compiled with Java [N]
    • ucp.jar:

      The Universal Connection Pool for JDBC
    • ojdbc[N]dms.jar:

      The Oracle Database JDBC driver compiled with Java [N] including the Dynamic Monitoring System (DMS)

      Note: ojdbc8dms.jar and ojdbc10dms.jar contain the instrumentation to support the Dynamic Monitoring System (DMS) and limited support for java.util.logging.

  • oracle.database.jdbc.debug: this group contains all JDBC debug libraries
  • oracle.database.security: this group contains all Security libraries for Oracle wallet and more
    • oraclepki.jar:

      The Oracle PKI provider used for Oracle wallets
    • osdt_cert.jar:

      Certificate management components used for Oracle wallets
    • osdt_core.jar:

      Core components between oraclepki.jar and osdt_cert.jar
  • oracle.database.ha: this group contains all High Availability libraries
    • ons.jar:

      Oracle Notification System library
    • simplefan.jar:

      Simple Fast Application Notification library
  • oracle.database.nls: this group contains the Internationalization library
    • orai18n.jar:

      orainternationalization.jar –> orai – 18 letters in between – n.jar
  • oracle.database.xml: this group contains all XML and XML DB related libraries
    • xdb.jar, xdb6.jar

      Support for the JDBC 4.x standard java.sql.SQLXML interface
    • xmlparserv2.jar

      The Oracle Database XML Parser library, including APIs for:

      • DOM and Simple API for XML (SAX) parsers
      • XML Schema processor
      • Extensible Stylesheet Language Transformation (XSLT) processor
      • XML compression
      • Java API for XML Processing (JAXP)
      • Utility functionality such as XMLSAXSerializer and asynchronous DOM Builder

        Note: xdb6.jar is a legacy name, xdb.jar is the new name.

  • oracle.database.observability: this group contains the Observability library
    • dms.jar:

      The Oracle Database Dynamic Monitoring System (DMS)
  • oracle.database.soda (coming soon!): this group contains the Simple Oracle Document Access driver for Oracle Database
  • oracle.database.messaging (coming soon!): this group contains the Advanced Queuing Java Messaging Service driver for Oracle Database

With this change, Oracle made it easier than ever before for developers and users alike to consume the Oracle Database Java client libraries.

Related:

Authentication via VS Code

I need a solution

Hey all,

i’m new to symantec DLP and i’m trying now to write JAVA code which will allow me to access to my Symantec DLP account. By following the steps in “Symantec™ Data Loss Prevention Incident Reporting and Update API Developers Guide” i knew that the user must have some privilege and have a specific jar in my JAVA code which contains specifics methods. This jar will allow java code to communicate with DLP Plateforme. Unfortunately during the execution of my code, this shows me the following error. Can anyone help me to solve this error ?

Best regards.

 Non unique body parts! In a port, as per BP 1.1 R2710 operations must have unique operation signature on the wire for successful dispatch. Methods [listCustomAttributes, listIncidentStatus] have the same request body block . Method dispatching may fail, runtime will try to dispatch using SOAPAction. Another option is to enable AddressingFeature to enabled runtime to uniquely identify WSDL operation using wsa:Action header.
 
0

Related: