1. Java Developer's Guide
  2. Changes in This Release for Oracle Database Java Developer's Guide

Changes in This Release for Oracle Database Java Developer's Guide

This preface contains:

Changes in Oracle Database 12c Release 2 (12.2.0.1)

The following are changes in Oracle Database Java Developer's Guide for Oracle Database 12c Release 2 (12.2.0.1).

New Features

The following features are new in this release:

  • Oracle JVM Web Services Call-Out Utility

    See "About Using Oracle JVM Web Services Call-Out Utility"

  • Support for Java 8

    See "Support for Java 8"

  • Oracle JVM Support for Running JavaScript in the database

    See "About Using Nashorn JavaScript Engine"

  • Improvements to Java Debug Wire Protocol (JDWP)

    See "Debugging Java Stored Procedures"

  • Oracle JVM Support for Long Identifiers

    Starting from Oracle Database 12c Release 2 (12.2.0.1), the maximum length of a SQL identifier is 128 bytes for Oracle JVM. A longer maximum length for SQL identifiers provides better compatibility and integration with other RDBMS components. It also improves performance because there is little or no conversion needed between short names and long names in Oracle JVM.

    In Oracle Database 12c Release 1 (12.1.0.1), the maximum length of a SQL identifier or a database schema object name is 30 bytes, and all characters must be legal and convertible to the target database character set.

Desupported Features

The following features are no longer supported by Oracle. See Oracle Database Upgrade Guide for a complete list of desupported features in this release.

Desupport of JPublisher

All Oracle JPublisher features are desupported and unavailable in Oracle Database 12c Release 2 (12.2.0.1). Oracle recommends that you use the alternatives listed here:

  • To continue to use Web service callouts, Oracle recommends that you use the Oracle JVM Web Services Callout utility, which is a replacement for the Web Services Callout utility.

  • To replace other JPublisher automation capabilities, including mapping user-defined SQL types or SQL types, wrapping PL/SQL packages and similar capabilities, Oracle recommends that developers use explicit steps, such as precompiling code with SQLJ precompiler, building Java STRUCT classes, or using other prestructured options.

See Also:

My Oracle Support Note 1937939.1 for more information about JDeveloper deprecation and desupport:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1937939.1

Desupport of Server-Side SQLJ

Starting with Oracle Database 12c Release 2 (12.2.0.1), server-side SQLJ is desupported. SQLJ is currently supported only as a client-side command-line tool.